From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, dsahern@kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/3] neighbour: convert neigh_dump_info() to RCU
Date: Fri, 19 Apr 2024 11:40:26 +0000 [thread overview]
Message-ID: <171352682675.11045.4640653458191585742.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240418095106.3680616-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 18 Apr 2024 09:51:03 +0000 you wrote:
> Remove RTNL requirement for "ip neighbour show" command.
>
> Eric Dumazet (3):
> neighbour: add RCU protection to neigh_tables[]
> neighbour: fix neigh_dump_info() return value
> neighbour: no longer hold RTNL in neigh_dump_info()
>
> [...]
Here is the summary with links:
- [net-next,1/3] neighbour: add RCU protection to neigh_tables[]
https://git.kernel.org/netdev/net-next/c/f8f2eb9de69a
- [net-next,2/3] neighbour: fix neigh_dump_info() return value
https://git.kernel.org/netdev/net-next/c/7e4975f7e7fb
- [net-next,3/3] neighbour: no longer hold RTNL in neigh_dump_info()
https://git.kernel.org/netdev/net-next/c/ba0f78069423
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:[~2024-04-19 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 9:51 [PATCH net-next 0/3] neighbour: convert neigh_dump_info() to RCU Eric Dumazet
2024-04-18 9:51 ` [PATCH net-next 1/3] neighbour: add RCU protection to neigh_tables[] Eric Dumazet
2024-04-18 9:51 ` [PATCH net-next 2/3] neighbour: fix neigh_dump_info() return value Eric Dumazet
2024-04-18 9:51 ` [PATCH net-next 3/3] neighbour: no longer hold RTNL in neigh_dump_info() Eric Dumazet
2024-04-19 11:40 ` 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=171352682675.11045.4640653458191585742.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--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.