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, petrm@nvidia.com,
andrew+netdev@lunn.ch
Subject: Re: [PATCH net-next 0/3] mlxsw: Make the driver ops-locked
Date: Tue, 21 Jul 2026 10:50:10 +0000 [thread overview]
Message-ID: <178463101064.226177.17488027333127938570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708123933.1303291-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 8 Jul 2026 15:39:30 +0300 you wrote:
> Make the driver ops-locked in order to allow ethtool operations to be
> invoked without RTNL being held.
>
> An ops-locked driver has most of its NDOs, all of its ethtool operations
> and some net device notifications run with the netdev instance lock
> held.
>
> [...]
Here is the summary with links:
- [net-next,1/3] mlxsw: Convert to async version of ndo_set_rx_mode
https://git.kernel.org/netdev/net-next/c/a5faaa079c61
- [net-next,2/3] mlxsw: ethtool: Prepare for RTNL-less ethtool operations
https://git.kernel.org/netdev/net-next/c/925a17fe4309
- [net-next,3/3] mlxsw: Tell the core to use the netdev instance lock
https://git.kernel.org/netdev/net-next/c/0501dd682648
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-07-21 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 12:39 [PATCH net-next 0/3] mlxsw: Make the driver ops-locked Ido Schimmel
2026-07-08 12:39 ` [PATCH net-next 1/3] mlxsw: Convert to async version of ndo_set_rx_mode Ido Schimmel
2026-07-08 12:39 ` [PATCH net-next 2/3] mlxsw: ethtool: Prepare for RTNL-less ethtool operations Ido Schimmel
2026-07-08 12:39 ` [PATCH net-next 3/3] mlxsw: Tell the core to use the netdev instance lock Ido Schimmel
2026-07-08 13:24 ` [PATCH net-next 0/3] mlxsw: Make the driver ops-locked Eric Dumazet
2026-07-21 10:50 ` 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=178463101064.226177.17488027333127938570.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--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