From: David Ahern <dsahern@gmail.com>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"greg@kroah.com" <greg@kroah.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH net] ipv6: Default fib6_type to RTN_UNICAST when not set
Date: Tue, 27 Aug 2019 11:51:32 -0600 [thread overview]
Message-ID: <b644d367-53a3-c2cc-2a84-28a7caae480c@gmail.com> (raw)
In-Reply-To: <db87d29f160302789f239cda2074ed35ae67da62.camel@infinera.com>
On 8/27/19 11:24 AM, Joakim Tjernlund wrote:
> On Tue, 2019-08-27 at 19:07 +0200, Greg KH wrote:
>>
>> On Tue, Aug 27, 2019 at 08:33:28AM +0000, Joakim Tjernlund wrote:
>>> I don't see the above patch in stable yet, is it still queued?
>>> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.spinics.net%2Flists%2Fnetdev%2Fmsg579581.html&data=02%7C01%7CJoakim.Tjernlund%40infinera.com%7Ce70efa27d90b4eecb1cf08d72b110e78%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C1%7C637025224574216531&sdata=Mhu0BqlM21XXYdR%2BC%2F8wXrMkzBKJpKUZZZXz57sAyuQ%3D&reserved=0
>>
>> Ask the network developers :)
>
> OK, asking netdev then.
>
> Jocke
>
Dave:
Specific request is for commit c7036d97acd2527cef145b5ef9ad1a37ed21bbe6
("ipv6: Default fib6_type to RTN_UNICAST when not set") to be queued for
stable releases prior to v5.2
next prev parent reply other threads:[~2019-08-27 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8dad6e3cf2e6cb0086b0a6f75ccdb44822a15001.camel@infinera.com>
[not found] ` <20190827170729.GD21369@kroah.com>
2019-08-27 17:24 ` [PATCH net] ipv6: Default fib6_type to RTN_UNICAST when not set Joakim Tjernlund
2019-08-27 17:51 ` David Ahern [this message]
2019-08-27 21:21 ` David Miller
2019-06-19 17:50 David Ahern
2019-06-19 21:15 ` David Miller
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=b644d367-53a3-c2cc-2a84-28a7caae480c@gmail.com \
--to=dsahern@gmail.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).