From: Ido Schimmel <idosch@nvidia.com>
To: Guillaume Nault <gnault@redhat.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
David Ahern <dsahern@kernel.org>, Aiden Yang <ling@moedove.com>,
Gary Guo <gary@kernel.org>
Subject: Re: [PATCH net 2/2] selftests: Add IPv6 multicast route generation tests for GRE devices.
Date: Thu, 10 Jul 2025 14:33:20 +0300 [thread overview]
Message-ID: <aG-lAN-qXs94BgWl@shredder> (raw)
In-Reply-To: <65a89583bde3bf866a1922c2e5158e4d72c520e2.1752070620.git.gnault@redhat.com>
On Wed, Jul 09, 2025 at 04:30:17PM +0200, Guillaume Nault wrote:
> The previous patch fixes a bug that prevented the creation of the
> default IPv6 multicast route (ff00::/8) for some GRE devices. Now let's
> extend the GRE IPv6 selftests to cover this case.
>
> Also, rename check_ipv6_ll_addr() to check_ipv6_device_config() and
> adapt comments and script output to take into account the fact that
> we're not limitted to link-local address generation.
In case you have v2: s/limitted/limited/
>
> Signed-off-by: Guillaume Nault <gnault@redhat.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2025-07-10 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 14:30 [PATCH net 0/2] gre: Fix default IPv6 multicast route creation Guillaume Nault
2025-07-09 14:30 ` [PATCH net 1/2] gre: Fix " Guillaume Nault
2025-07-10 11:32 ` Ido Schimmel
2025-07-10 12:57 ` Gary Guo
2025-07-11 17:07 ` Guillaume Nault
2025-07-09 14:30 ` [PATCH net 2/2] selftests: Add IPv6 multicast route generation tests for GRE devices Guillaume Nault
2025-07-10 11:33 ` Ido Schimmel [this message]
2025-07-11 16:56 ` Guillaume Nault
2025-07-11 1:30 ` [PATCH net 0/2] gre: Fix default IPv6 multicast route creation patchwork-bot+netdevbpf
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=aG-lAN-qXs94BgWl@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gary@kernel.org \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=ling@moedove.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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