REPORTING-BUGS
PATCH 3/9 REPORTING-BUGS
- missing word added
- second blank behind sentence added, as in rest of document
Signed-off-by Markus Osterhoff <[email protected]>
--- REPORTING-BUGS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
REPORTING-BUGS +2 -2
@@ -9,7 +9,7 @@ Please see https://www.kernel.org/ for a list of supported kernels. Any kernel marked with [EOL] is "end of life" and will not have any fixes backported to it. -If you've found a bug on a kernel version isn't listed on kernel.org, +If you've found a bug on a kernel version that isn't listed on kernel.org, contact your Linux distribution or embedded vendor for support. Alternatively, you can attempt to run one of the supported stable or -rc kernels, and see if you can reproduce the bug on that. It's preferable
@@ -88,7 +88,7 @@ step-by-step instructions for how a user can trigger the bug. If the failure includes an "OOPS:", take a picture of the screen, capture a netconsole trace, or type the message from your screen into the bug report. Please read "Documentation/oops-tracing.txt" before posting your -bug report. This explains what you should do with the "Oops" information +bug report. This explains what you should do with the "Oops" information to make it useful to the recipient. This is a suggested format for a bug report sent via email or bugzilla.
Signature · 1 line
1.8.5.5