Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9dcbb32f authored by Tobias Klauser's avatar Tobias Klauser Committed by Linus Torvalds
Browse files

[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: default avatarTobias Klauser <tklauser@nuerscht.ch>
Signed-off-by: default avatarDomen Puncer <domen@coderock.org>
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent 96757701

REPORTING-BUGS

+7 −7
Original line number Diff line number Diff line
@@ -9,7 +9,7 @@ screen please read "Documentation/oops-tracing.txt" before posting your 
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
@@ -18,7 +18,7 @@ The list of maintainers is in the MAINTAINERS file in this directory. 


      If it is a security bug, please copy the Security Contact listed

in the MAINTAINERS file.  They can help coordinate bugfix and disclosure.

See Documentation/SecurityBugs for more infomation.

See Documentation/SecurityBugs for more information.



      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
@@ -35,7 +35,7 @@ the command "sh scripts/ver_linux". 


Use that information to fill in all fields of the bug report form, and

post it to the mailing list with a subject of "PROBLEM: <one line

summary from [1.]>" for easy identification by the developers    

summary from [1.]>" for easy identification by the developers.



[1.] One line summary of the problem:

[2.] Full description of the problem/report: