From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, ndesaulniers@google.com
Subject: Re: [PATCH net v2 0/2] ipv6: fix neighbour resolution with raw socket
Date: Mon, 14 Oct 2019 11:34:05 +0200 [thread overview]
Message-ID: <61611bc6-fd77-e46e-55ee-e0d5cff37ae8@6wind.com> (raw)
In-Reply-To: <20190626.132634.1369555115978417142.davem@davemloft.net>
Le 26/06/2019 à 22:26, David Miller a écrit :
> From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Date: Mon, 24 Jun 2019 16:01:07 +0200
>
>> The first patch prepares the fix, it constify rt6_nexthop().
>> The detail of the bug is explained in the second patch.
>>
>> v1 -> v2:
>> - fix compilation warnings
>> - split the initial patch
>
> Series applied, thanks Nicolas.
>
Is it possible to queue this for the stable trees?
Thank you,
Nicolas
prev parent reply other threads:[~2019-10-14 9:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 12:34 [PATCH net] ipv6: fix neighbour resolution with raw socket Nicolas Dichtel
2019-06-20 15:12 ` David Ahern
2019-06-20 15:42 ` Nicolas Dichtel
2019-06-20 16:36 ` David Ahern
2019-06-20 16:47 ` David Ahern
2019-06-21 8:09 ` Nicolas Dichtel
2019-06-21 18:48 ` kbuild test robot
2019-06-23 0:07 ` David Miller
2019-06-23 0:08 ` David Miller
2019-06-24 14:01 ` [PATCH net v2 0/2] " Nicolas Dichtel
2019-06-24 14:01 ` [PATCH net v2 1/2] ipv6: constify rt6_nexthop() Nicolas Dichtel
2019-06-24 16:45 ` Nick Desaulniers
2019-06-24 17:06 ` David Miller
2019-06-24 17:17 ` Nick Desaulniers
2019-06-24 17:22 ` David Miller
2019-06-24 17:37 ` Nick Desaulniers
2019-06-24 18:18 ` Nicolas Dichtel
2019-06-24 20:27 ` David Miller
2019-06-24 14:01 ` [PATCH net v2 2/2] ipv6: fix neighbour resolution with raw socket Nicolas Dichtel
2019-06-26 20:26 ` [PATCH net v2 0/2] " David Miller
2019-10-14 9:34 ` Nicolas Dichtel [this message]
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=61611bc6-fd77-e46e-55ee-e0d5cff37ae8@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=ndesaulniers@google.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.