[PATCH 4.17 06/15] netdev-FAQ: clarify DaveMs position for stable backports

From: Greg Kroah-Hartman
Date: Sat Jun 09 2018 - 11:31:21 EST

4.17-stable review patch. If anyone has any objections, please let me know.


From: Cong Wang <xiyou.wangcong@xxxxxxxxx>

[ Upstream commit 75d4e704fa8d2cf33ff295e5b441317603d7f9fd ]

Per discussion with David at netconf 2018, let's clarify
DaveM's position of handling stable backports in netdev-FAQ.

This is important for people relying on upstream -stable

Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Cong Wang <xiyou.wangcong@xxxxxxxxx>
Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Documentation/networking/netdev-FAQ.txt | 9 +++++++++
1 file changed, 9 insertions(+)

--- a/Documentation/networking/netdev-FAQ.txt
+++ b/Documentation/networking/netdev-FAQ.txt
@@ -179,6 +179,15 @@ A: No. See above answer. In short, if
dash marker line as described in Documentation/process/submitting-patches.rst to
temporarily embed that information into the patch that you send.

+Q: Are all networking bug fixes backported to all stable releases?
+A: Due to capacity, Dave could only take care of the backports for the last
+ 2 stable releases. For earlier stable releases, each stable branch maintainer
+ is supposed to take care of them. If you find any patch is missing from an
+ earlier stable branch, please notify stable@xxxxxxxxxxxxxxx with either a
+ commit ID or a formal patch backported, and CC Dave and other relevant
+ networking developers.
Q: Someone said that the comment style and coding convention is different
for the networking content. Is this true?