From: "J. Bruce Fields" People should also cc relevant mailing lists when reporting bugs. Signed-off-by: J. Bruce Fields Acked-by: Randy Dunlap Signed-off-by: Andrew Morton --- REPORTING-BUGS | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff -puN REPORTING-BUGS~reporting-bugs-cc-the-mailing-list-too REPORTING-BUGS --- a/REPORTING-BUGS~reporting-bugs-cc-the-mailing-list-too +++ a/REPORTING-BUGS @@ -10,11 +10,12 @@ bug report. This explains what you shoul 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. _