1 files changed, 6 insertions, 5 deletions
diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index ac02e42a262..ab0c56630a8 100644
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS
@@ -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
+be involved with the problem, and cc the relevant mailing list. Don't
-wrong person. If you are unsure send it to the person responsible for the
+worry too much about getting the wrong person. If you are unsure send it
-code relevant to what you were doing. If it occurs repeatably try and
+to the person responsible for the code relevant to what you were doing.
-describe how to recreate it. That is worth even more than the oops itself.
+If it occurs repeatably try and describe how to recreate it. That is
-The list of maintainers is in the MAINTAINERS file in this directory.
+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.

diff --git a/REPORTING-BUGS b/REPORTING-BUGS index ac02e42a262..ab0c56630a8 100644 --- a/REPORTING-BUGS +++ b/REPORTING-BUGS
@@ -10,11 +10,12 @@ bug report. This explains what you should do with the "Oops" information
10	to make it useful to the recipient.	10	to make it useful to the recipient.
11		11
12	Send the output to the maintainer of the kernel area that seems to	12	Send the output to the maintainer of the kernel area that seems to
13	be involved with the problem. Don't worry too much about getting the	13	be involved with the problem, and cc the relevant mailing list. Don't
14	wrong person. If you are unsure send it to the person responsible for the	14	worry too much about getting the wrong person. If you are unsure send it
15	code relevant to what you were doing. If it occurs repeatably try and	15	to the person responsible for the code relevant to what you were doing.
16	describe how to recreate it. That is worth even more than the oops itself.	16	If it occurs repeatably try and describe how to recreate it. That is
17	The list of maintainers is in the MAINTAINERS file in this directory.	17	worth even more than the oops itself. The list of maintainers and
		18	mailing lists is in the MAINTAINERS file in this directory.
18		19
19	If it is a security bug, please copy the Security Contact listed	20	If it is a security bug, please copy the Security Contact listed
20	in the MAINTAINERS file. They can help coordinate bugfix and disclosure.	21	in the MAINTAINERS file. They can help coordinate bugfix and disclosure.