Commit 3ab32df7 authored by J. Bruce Fields's avatar J. Bruce Fields Committed by Linus Torvalds
Browse files

REPORTING-BUGS: cc the mailing list too 



People should also cc relevant mailing lists when reporting bugs.

Signed-off-by: default avatarJ. Bruce Fields <bfields@citi.umich.edu>
Acked-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 9b8eae72

REPORTING-BUGS

+6 −5
Original line number Diff line number Diff line
@@ -10,11 +10,12 @@ 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. 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 is in the MAINTAINERS file in this directory.

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 it is a security bug, please copy the Security Contact listed

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