aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTobias Klauser2005-09-10 02:26:58 -0500
committerLinus Torvalds2005-09-10 12:06:31 -0500
commit9dcbb32f1654e79c212c20d9cd9d48509ee1eaf7 (patch)
treeb0663a525fbb0f24acc6304d6869b71d0c0c991c /REPORTING-BUGS
parent96757701336365e30bea9fccdfac087338954e09 (diff)
downloadkernel-omap-9dcbb32f1654e79c212c20d9cd9d48509ee1eaf7.tar.gz
kernel-omap-9dcbb32f1654e79c212c20d9cd9d48509ee1eaf7.tar.xz
kernel-omap-9dcbb32f1654e79c212c20d9cd9d48509ee1eaf7.zip
[PATCH] Spelling and whitespace fixes for REPORTING-BUGS
The attached patch fixes some spelling errors in REPORTING-BUGS and also removes all trailing whitespaces. Signed-off-by: Tobias Klauser <tklauser@nuerscht.ch> Signed-off-by: Domen Puncer <domen@coderock.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'REPORTING-BUGS')
-rw-r--r--REPORTING-BUGS14
1 files changed, 7 insertions, 7 deletions
diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index 224c34741d32..f9da827a0c18 100644
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS
@@ -9,7 +9,7 @@ screen please read "Documentation/oops-tracing.txt" before posting your
9bug report. This explains what you should do with the "Oops" information 9bug report. This explains what you should do with the "Oops" information
10to make it useful to the recipient. 10to make it useful to the recipient.
11 11
12 Send the output the maintainer of the kernel area that seems to 12 Send the output to the maintainer of the kernel area that seems to
13be involved with the problem. Don't worry too much about getting the 13be involved with the problem. Don't worry too much about getting the
14wrong person. If you are unsure send it to the person responsible for the 14wrong person. If you are unsure send it to the person responsible for the
15code relevant to what you were doing. If it occurs repeatably try and 15code relevant to what you were doing. If it occurs repeatably try and
@@ -18,15 +18,15 @@ The list of maintainers is in the MAINTAINERS file in this directory.
18 18
19 If it is a security bug, please copy the Security Contact listed 19 If it is a security bug, please copy the Security Contact listed
20in the MAINTAINERS file. They can help coordinate bugfix and disclosure. 20in the MAINTAINERS file. They can help coordinate bugfix and disclosure.
21See Documentation/SecurityBugs for more infomation. 21See Documentation/SecurityBugs for more information.
22 22
23 If you are totally stumped as to whom to send the report, send it to 23 If you are totally stumped as to whom to send the report, send it to
24linux-kernel@vger.kernel.org. (For more information on the linux-kernel 24linux-kernel@vger.kernel.org. (For more information on the linux-kernel
25mailing list see http://www.tux.org/lkml/). 25mailing list see http://www.tux.org/lkml/).
26 26
27This is a suggested format for a bug report sent to the Linux kernel mailing 27This is a suggested format for a bug report sent to the Linux kernel mailing
28list. Having a standardized bug report form makes it easier for you not to 28list. Having a standardized bug report form makes it easier for you not to
29overlook things, and easier for the developers to find the pieces of 29overlook things, and easier for the developers to find the pieces of
30information they're really interested in. Don't feel you have to follow it. 30information they're really interested in. Don't feel you have to follow it.
31 31
32 First run the ver_linux script included as scripts/ver_linux, which 32 First run the ver_linux script included as scripts/ver_linux, which
@@ -35,9 +35,9 @@ the command "sh scripts/ver_linux".
35 35
36Use that information to fill in all fields of the bug report form, and 36Use that information to fill in all fields of the bug report form, and
37post it to the mailing list with a subject of "PROBLEM: <one line 37post it to the mailing list with a subject of "PROBLEM: <one line
38summary from [1.]>" for easy identification by the developers 38summary from [1.]>" for easy identification by the developers.
39 39
40[1.] One line summary of the problem: 40[1.] One line summary of the problem:
41[2.] Full description of the problem/report: 41[2.] Full description of the problem/report:
42[3.] Keywords (i.e., modules, networking, kernel): 42[3.] Keywords (i.e., modules, networking, kernel):
43[4.] Kernel version (from /proc/version): 43[4.] Kernel version (from /proc/version):