renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-10 22:33:54 +08:00
Code

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

Browse Source 
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: Sarah Sharp <sarah.a.sharp@linux.intel.com>
This commit is contained in:
Sarah Sharp 2013-04-13 17:55:18 -07:00
parent bb33db7a07
commit 3b12c21ab3
1 changed files with 22 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
REPORTING-BUGS
View File

@ -1,30 +1,31 @@
[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ] [Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
What follows is a suggested procedure for reporting Linux bugs. You What follows is a suggested procedure for reporting Linux bugs. You aren't
aren't obliged to use the bug reporting format, it is provided as a guide obliged to use the bug reporting format, it is provided as a guide to the
to the kind of information that can be useful to developers - no more. kind of information that can be useful to developers - no more.
If the failure includes an "OOPS:" type message in your log or on If the failure includes an "OOPS:" type message in your log or on screen
screen please read "Documentation/oops-tracing.txt" before posting your please read "Documentation/oops-tracing.txt" before posting your bug
bug report. This explains what you should do with the "Oops" information report. This explains what you should do with the "Oops" information to
to make it useful to the recipient. 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> perl scripts/get_maintainer.pl -f <filename>
If it is a security bug, please copy the Security Contact listed If it is a security bug, please copy the Security Contact listed in the
in the MAINTAINERS file. They can help coordinate bugfix and disclosure. MAINTAINERS file. They can help coordinate bugfix and disclosure. See
See Documentation/SecurityBugs for more information. Documentation/SecurityBugs for more information.
If you are totally stumped as to whom to send the report, send it to 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 linux-kernel@vger.kernel.org. (For more information on the linux-kernel
mailing list see http://www.tux.org/lkml/). mailing list see http://www.tux.org/lkml/).
@ -33,7 +34,7 @@ list. Having a standardized bug report form makes it easier for you not to
overlook things, and easier for the developers to find the pieces of overlook things, and easier for the developers to find the pieces of
information they're really interested in. Don't feel you have to follow it. information they're really interested in. Don't feel you have to follow it.
First run the ver_linux script included as scripts/ver_linux, which First run the ver_linux script included as scripts/ver_linux, which
reports the version of some important subsystems. Run this script with reports the version of some important subsystems. Run this script with
the command "sh scripts/ver_linux". the command "sh scripts/ver_linux".