public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: 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,
	Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next v2 0/3] vrf: A few cleanups
Date: Thu, 26 Mar 2026 22:32:30 +0200	[thread overview]
Message-ID: <20260326203233.1128554-1-idosch@nvidia.com> (raw)

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.

v1: https://lore.kernel.org/netdev/20260324155521.525292-1-idosch@nvidia.com/

Ido Schimmel (3):
  vrf: Remove unnecessary NULL check
  vrf: Use dst_dev_put() instead of using loopback device
  vrf: Remove unnecessary RCU protection around dst entries

 drivers/net/vrf.c | 82 +++++++++--------------------------------------
 1 file changed, 16 insertions(+), 66 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-03-26 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 20:32 Ido Schimmel [this message]
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

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=20260326203233.1128554-1-idosch@nvidia.com \
    --to=idosch@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.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