From: patchwork-bot+netdevbpf@kernel.org
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, kuniyu@google.com, dsahern@kernel.org
Subject: Re: [PATCH net 0/2] neighbour: fix update of proxy neighbour
Date: Thu, 12 Mar 2026 02:10:14 +0000 [thread overview]
Message-ID: <177328141454.3905617.15461656435350206907.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1772894876.git.sd@queasysnail.net>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Mar 2026 22:59:15 +0100 you wrote:
> While re-reading some "old" patches I ran into a small change of
> behavior in commit dc2a27e524ac ("neighbour: Update pneigh_entry in
> pneigh_create().").
>
> The old behavior was not consistent between ->protocol and ->flags,
> and didn't offer a way to clear protocol, so maybe it's better to
> change that (7-years-old [1]) behavior. But then we should change
> non-proxy neighbours as well to keep neigh/pneigh consistent.
>
> [...]
Here is the summary with links:
- [net,1/2] neighbour: restore protocol != 0 check in pneigh update
https://git.kernel.org/netdev/net/c/cbada1048847
- [net,2/2] selftests: rtnetlink: add neighbour update test
https://git.kernel.org/netdev/net/c/68e76fc12df0
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:[~2026-03-12 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 21:59 [PATCH net 0/2] neighbour: fix update of proxy neighbour Sabrina Dubroca
2026-03-10 21:59 ` [PATCH net 1/2] neighbour: restore protocol != 0 check in pneigh update Sabrina Dubroca
2026-03-10 23:16 ` David Ahern
2026-03-11 4:04 ` Kuniyuki Iwashima
2026-03-10 21:59 ` [PATCH net 2/2] selftests: rtnetlink: add neighbour update test Sabrina Dubroca
2026-03-11 4:10 ` Kuniyuki Iwashima
2026-03-12 2:10 ` 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=177328141454.3905617.15461656435350206907.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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