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

Commit 3b12c21a authored by Sarah Sharp's avatar Sarah Sharp
Browse files

Trivial: docs: Remove six-space indentation in REPORTING-BUGS. 



Other paragraph format docs in Documentation don't use paragraph
indentations, so conform REPORTING-BUGS to that.

Re-wrap the paragraphs, keeping the doc to a 74-character line length,
since that's what the original seemed to use.

Signed-off-by: default avatarSarah Sharp <sarah.a.sharp@linux.intel.com>
parent bb33db7a

REPORTING-BUGS

+22 −21
Original line number Diff line number Diff line 
[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]



     What follows is a suggested procedure for reporting Linux bugs. You

aren't obliged to use the bug reporting format, it is provided as a guide

to the kind of information that can be useful to developers - no more.

What follows is a suggested procedure for reporting Linux bugs. You aren't

obliged to use the bug reporting format, it is provided as a guide to the

kind of information that can be useful to developers - no more.



     If the failure includes an "OOPS:" type message in your log or on

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.

If the failure includes an "OOPS:" type message in your log or on 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 to the maintainer of the kernel area that seems to be

involved with the problem, and cc the relevant mailing list. 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 describe how to recreate it. That is worth even

more than the oops itself.  The list of maintainers and mailing lists is

in the MAINTAINERS file in this directory.  If you know the file name that

causes the problem you can use the following command in this directory to

find some of the maintainers of that file:



      Send the output to the maintainer of the kernel area that seems to

be involved with the problem, and cc the relevant mailing list. 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 describe how to recreate it. That is

worth even more than the oops itself.  The list of maintainers and

mailing lists is in the MAINTAINERS file in this directory.  If you

know the file name that causes the problem you can use the following

command in this directory to find some of the maintainers of that file:

     perl scripts/get_maintainer.pl -f <filename>



      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 information.

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