From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?TWFoZXNoIEJhbmRld2FyICjgpK7gpLngpYfgpLYg4KSs4KSC4KSh4KWH4KS14KS+?=@ci.codeaurora.org,
=?utf-8?b?4KSwKSA8bWFoZXNoYkBnb29nbGUuY29tPg==?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, dsahern@kernel.org, davem@davemloft.net,
kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
corbet@lwn.net, mahesh@bandewar.net, kuniyu@amazon.com,
maze@google.com
Subject: Re: [PATCHv2 next] ipv6: add icmpv6_error_anycast_as_unicast for ICMPv6
Date: Fri, 21 Apr 2023 03:30:18 +0000 [thread overview]
Message-ID: <168204781899.6790.87891683637213829.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230419013238.2691167-1-maheshb@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Apr 2023 18:32:38 -0700 you wrote:
> ICMPv6 error packets are not sent to the anycast destinations and this
> prevents things like traceroute from working. So create a setting similar
> to ECHO when dealing with Anycast sources (icmpv6_echo_ignore_anycast).
>
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
> CC: Maciej Żenczykowski <maze@google.com>
>
> [...]
Here is the summary with links:
- [PATCHv2,next] ipv6: add icmpv6_error_anycast_as_unicast for ICMPv6
https://git.kernel.org/netdev/net-next/c/7ab75456be14
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-21 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 1:32 [PATCHv2 next] ipv6: add icmpv6_error_anycast_as_unicast for ICMPv6 Mahesh Bandewar
2023-04-20 18:55 ` David Ahern
2023-04-20 19:12 ` Maciej Żenczykowski
2023-04-20 21:00 ` Mahesh Bandewar (महेश बंडेवार)
2023-04-21 3:30 ` patchwork-bot+netdevbpf [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=168204781899.6790.87891683637213829.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?4KSwKSA8bWFoZXNoYkBnb29nbGUuY29tPg==?=@ci.codeaurora.org \
--cc==?utf-8?b?TWFoZXNoIEJhbmRld2FyICjgpK7gpLngpYfgpLYg4KSs4KSC4KSh4KWH4KS14KS+?=@ci.codeaurora.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=mahesh@bandewar.net \
--cc=maze@google.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 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.