Eric Lee / linux-smarc-t335x-v3.2

Download as
Browse Code ยป

Commit 9dcbb32f1654e79c212c20d9cd9d48509ee1eaf7

Authored by Tobias Klauser
Committed by Linus Torvalds
1 parent 9675770133

[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>

Showing 1 changed file with 7 additions and 7 deletions Side-by-side Diff

... ... @@ -9,7 +9,7 @@
9 9 bug report. This explains what you should do with the "Oops" information
10 10 to 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
13 13 be involved with the problem. Don't worry too much about getting the
14 14 wrong person. If you are unsure send it to the person responsible for the
15 15 code relevant to what you were doing. If it occurs repeatably try and
16 16  
... ... @@ -18,15 +18,15 @@
18 18  
19 19 If it is a security bug, please copy the Security Contact listed
20 20 in the MAINTAINERS file. They can help coordinate bugfix and disclosure.
21   -See Documentation/SecurityBugs for more infomation.
  21 +See Documentation/SecurityBugs for more information.
22 22  
23 23 If you are totally stumped as to whom to send the report, send it to
24 24 linux-kernel@vger.kernel.org. (For more information on the linux-kernel
25 25 mailing list see http://www.tux.org/lkml/).
26 26  
27   -This is a suggested format for a bug report sent to the Linux kernel mailing
28   -list. Having a standardized bug report form makes it easier for you not to
29   -overlook things, and easier for the developers to find the pieces of
  27 +This is a suggested format for a bug report sent to the Linux kernel mailing
  28 +list. Having a standardized bug report form makes it easier for you not to
  29 +overlook things, and easier for the developers to find the pieces of
30 30 information they're really interested in. Don't feel you have to follow it.
31 31  
32 32 First run the ver_linux script included as scripts/ver_linux, which
33 33  
... ... @@ -35,9 +35,9 @@
35 35  
36 36 Use that information to fill in all fields of the bug report form, and
37 37 post it to the mailing list with a subject of "PROBLEM: <one line
38   -summary from [1.]>" for easy identification by the developers
  38 +summary 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 41 [2.] Full description of the problem/report:
42 42 [3.] Keywords (i.e., modules, networking, kernel):
43 43 [4.] Kernel version (from /proc/version):