| Message ID | 20180604180719.6053-1-xiyou.wangcong@gmail.com |
|---|---|
| State | Changes Requested, archived |
| Delegated to: | David Miller |
| Headers | show |
| Series | [net-next] netdev-FAQ: clarify DaveM's position for stable backports | expand |
On Mon, Jun 04, 2018 at 11:07:19AM -0700, Cong Wang wrote: > 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: stable@vger.kernel.org > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> > Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com> > --- > Documentation/networking/netdev-FAQ.txt | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/Documentation/networking/netdev-FAQ.txt b/Documentation/networking/netdev-FAQ.txt > index 2a3278d5cf35..6dde6686c870 100644 > --- a/Documentation/networking/netdev-FAQ.txt > +++ b/Documentation/networking/netdev-FAQ.txt > @@ -179,6 +179,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 > + 3 stable releases. For earlier stable releases, each stable branch maintainer s/3/2/ There's no need for Dave to do more work than he currently does :) thanks, greg k-h
From: Cong Wang <xiyou.wangcong@gmail.com> Date: Mon, 4 Jun 2018 11:07:19 -0700 > +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 > + 3 stable releases. As Greg stated, I only do 2 not 3.
On Tue, Jun 5, 2018 at 6:43 AM, David Miller <davem@davemloft.net> wrote: > From: Cong Wang <xiyou.wangcong@gmail.com> > Date: Mon, 4 Jun 2018 11:07:19 -0700 > >> +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 >> + 3 stable releases. > > As Greg stated, I only do 2 not 3. Sure, will send v2. We just need a number here. :) Thanks!
diff --git a/Documentation/networking/netdev-FAQ.txt b/Documentation/networking/netdev-FAQ.txt index 2a3278d5cf35..6dde6686c870 100644 --- a/Documentation/networking/netdev-FAQ.txt +++ b/Documentation/networking/netdev-FAQ.txt @@ -179,6 +179,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 + 3 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?
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: stable@vger.kernel.org Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com> --- Documentation/networking/netdev-FAQ.txt | 9 +++++++++ 1 file changed, 9 insertions(+)