From: David Miller <davem@davemloft.net>
To: xiyou.wangcong@gmail.com
Cc: pmenzel@molgen.mpg.de, edumazet@google.com,
netdev@vger.kernel.org, ast@kernel.org,
it+linux-netdev@molgen.mpg.de, gregkh@linuxfoundation.org
Subject: Re: Cherry pick commit *net: better skb->sender_cpu and skb->napi_id cohabitation* to 4.4 series?
Date: Fri, 02 Jun 2017 14:37:19 -0400 (EDT) [thread overview]
Message-ID: <20170602.143719.124343853677571075.davem@davemloft.net> (raw)
In-Reply-To: <CAM_iQpXg3XCyfi7kStkWOh3R4+0yQHN15MOZ2dkbEYZvR1Xf2Q@mail.gmail.com>
From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Fri, 2 Jun 2017 10:51:39 -0700
> On Thu, Jun 1, 2017 at 10:32 AM, Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>> Dear David,
>>
>>
>> On 06/01/17 18:19, David Miller wrote:
>>>
>>> Neither of us have anything to do with the 4.4 -stable series. We only
>>> manage stable backport submissions for the most recent two releases.
>>
>>
>> Thank you for the prompt response. Should the netdev FAQ be updated then to
>> contain that information?
>
> +1
>
> It is quite helpful to know which stable releases contain network fixes
> which don't, especially for those who rely on stable releases, at least
> we could do backport by ourselves when we know they are missing.
The people who maintain the -stable releases older than the ones Greg KH
are doing typically scan the ones that Greg applies and tries to integrate
them into their -stable releases when appropriate.
If someone wants to write an accurate description of that and how it works,
and add it to the FAQ, sure.
next prev parent reply other threads:[~2017-06-02 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 12:43 Cherry pick commit *net: better skb->sender_cpu and skb->napi_id cohabitation* to 4.4 series? Paul Menzel
2017-06-01 16:19 ` David Miller
2017-06-01 17:32 ` Paul Menzel
2017-06-02 17:51 ` Cong Wang
2017-06-02 18:37 ` David Miller [this message]
2017-06-02 21:37 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170602.143719.124343853677571075.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=it+linux-netdev@molgen.mpg.de \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).