diff options
| author | Cong Wang <xiyou.wangcong@gmail.com> | 2018-06-05 09:48:13 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-06-11 22:49:19 +0200 |
| commit | be1f1827a89a1d57dd2c9dafc9b6ddc96e8b2ebe (patch) | |
| tree | 5998c9694d57921bd6c8b5b03fda6e3d7d924f9c /Documentation | |
| parent | c6fae49a447ca86d65922f92281d232c3adbb1db (diff) | |
| download | linux-stable-be1f1827a89a1d57dd2c9dafc9b6ddc96e8b2ebe.tar.gz linux-stable-be1f1827a89a1d57dd2c9dafc9b6ddc96e8b2ebe.tar.bz2 linux-stable-be1f1827a89a1d57dd2c9dafc9b6ddc96e8b2ebe.zip | |
netdev-FAQ: clarify DaveM's position for stable backports
[ 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
releases.
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/networking/netdev-FAQ.txt | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/Documentation/networking/netdev-FAQ.txt b/Documentation/networking/netdev-FAQ.txt index cfc66ea72329..a365656e4873 100644 --- a/Documentation/networking/netdev-FAQ.txt +++ b/Documentation/networking/netdev-FAQ.txt @@ -176,6 +176,15 @@ A: No. See above answer. In short, if you think it really belongs in 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@vger.kernel.org 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? |