Lines Matching refs:report
26 below for convenience. Two of them are important: start your report's subject
30 #. Optional, but recommended: when sending or forwarding your report, make the
73 How do I report a regression?
76 Just report the issue as outlined in
85 * Start your report's subject with "[REGRESSION]".
87 * In your report, clearly mention the last kernel version that worked fine and
92 (regressions@lists.linux.dev) know about your report:
94 * If you report the regression by mail, CC the regressions list.
96 * If you report your regression to some bug tracker, forward the submitted
97 report by mail to the regressions list while CCing the maintainer and the
107 When CCing for forwarding your report to the list, consider directly telling the
108 aforementioned Linux kernel regression tracking bot about your report. To do
113 Regzbot will then consider your mail a report for a regression introduced in the
122 report won't fall through the cracks unnoticed. If you omit this, the Linux
209 All of them are helped by people trying to ensure no regression report falls
213 your report on the radar of these people by CCing or forwarding each report to
261 tried their best to avoid the regression. If not, report it; if in doubt, ask
347 Can I report a regression I found with pre-compiled vanilla kernels?
352 some known-to-be incompatible feature for the newer kernel. If in doubt, report
401 report. The easiest way to do that: find the report in your "Sent" folder or the