From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, dsahern@kernel.org,
andrew+netdev@lunn.ch, petrm@nvidia.com, lirongqing@baidu.com
Subject: Re: [PATCH net-next v2 0/3] vrf: A few cleanups
Date: Sat, 28 Mar 2026 04:10:16 +0000 [thread overview]
Message-ID: <177467101604.4182342.17079713304515719113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260326203233.1128554-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Mar 2026 22:32:30 +0200 you wrote:
> Perform a few cleanups in the VRF driver. Noticed these while reviewing
> a recent patch [1]. See individual patches for more details.
>
> [1] https://lore.kernel.org/netdev/20260310105331.2371-1-lirongqing@baidu.com/
>
> v2:
> * In patch #3, remove RCU protection around dst entries instead of just
> the synchronize_rcu() calls.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] vrf: Remove unnecessary NULL check
https://git.kernel.org/netdev/net-next/c/ae3cdfd4e0b8
- [net-next,v2,2/3] vrf: Use dst_dev_put() instead of using loopback device
https://git.kernel.org/netdev/net-next/c/50504e2579c1
- [net-next,v2,3/3] vrf: Remove unnecessary RCU protection around dst entries
https://git.kernel.org/netdev/net-next/c/075196489a37
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-28 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 20:32 [PATCH net-next v2 0/3] vrf: A few cleanups Ido Schimmel
2026-03-26 20:32 ` [PATCH net-next v2 1/3] vrf: Remove unnecessary NULL check Ido Schimmel
2026-03-26 20:32 ` [PATCH net-next v2 2/3] vrf: Use dst_dev_put() instead of using loopback device Ido Schimmel
2026-03-26 20:32 ` [PATCH net-next v2 3/3] vrf: Remove unnecessary RCU protection around dst entries Ido Schimmel
2026-03-27 14:56 ` David Ahern
2026-03-28 4: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=177467101604.4182342.17079713304515719113.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=lirongqing@baidu.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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