lkml.org 
[lkml]   [2003]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
Subject[PATCH] REPORTING-BUGS

This patch adds some extra info for bug-reporting.


--- REPORTING-BUGS.orig Sun Feb 9 00:18:06 2003
+++ REPORTING-BUGS Sun Feb 9 00:32:00 2003
@@ -9,7 +9,7 @@
bug report. This explains what you should do with the "Oops" information
to make it useful to the recipient.

- Send the output the maintainer of the kernel area that seems to
+ Send the output to the maintainer of the kernel area that seems to
be involved with the problem. Don't worry too much about getting the
wrong person. If you are unsure send it to the person responsible for the
code relevant to what you were doing. If it occurs repeatably try and
@@ -19,6 +19,11 @@
If you are totally stumped as to whom to send the report, send it to
linux-kernel@vger.kernel.org. (For more information on the linux-kernel
mailing list see http://www.tux.org/lkml/).
+
+ Before sending the report, also make sure that you are getting the
+same oops with the later stable/development versions of your kernel (if any).
+There is a chance that it may have already been fixed in the later kernels.
+This may not be easy to see if the bug is not reproducible, though.

This is a suggested format for a bug report sent to the Linux kernel mailing
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.023 / U:10.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site