All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: jgg@ziepe.ca, leon@kernel.org, aleksandr.loktionov@intel.com,
	sdf.kernel@gmail.com, pabeni@redhat.com, tariqt@nvidia.com,
	sdf@fomichev.me, netdev@vger.kernel.org, cratiu@nvidia.com,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] IB/IPoIB: ndo_set_rx_mode_async conversion
Date: Sat, 16 May 2026 00:30:07 +0000	[thread overview]
Message-ID: <177889140739.207359.8985306017569918471.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260513124519.3357165-1-dtatulea@nvidia.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 13 May 2026 15:45:18 +0300 you wrote:
> The commit in the fixes tag added a warning for devices
> that are netdev ops locked that they should be converted
> to .ndo_set_rx_mode_async. IPoIB for mlx5 is such a
> driver which was missed during the conversion because the
> flow is more complex:
> - mlx5 part of IPoIB device was converted to ops-lock in commit [1].
> - ipoib_intf_init() then overrides netdev_ops with
>   ipoib_netdev_ops_{pf,vf}, which still wired ndo_set_rx_mode to the
>   legacy sync path -- tripping the new warning on every probe.
> 
> [...]

Here is the summary with links:
  - [net] IB/IPoIB: ndo_set_rx_mode_async conversion
    https://git.kernel.org/netdev/net/c/cfd08f09723c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-05-16  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 12:45 [PATCH net] IB/IPoIB: ndo_set_rx_mode_async conversion Dragos Tatulea
2026-05-14 23:42 ` Jakub Kicinski
2026-05-15 11:51   ` Jason Gunthorpe
2026-05-16  0:30 ` 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=177889140739.207359.8985306017569918471.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aleksandr.loktionov@intel.com \
    --cc=cratiu@nvidia.com \
    --cc=dtatulea@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf.kernel@gmail.com \
    --cc=sdf@fomichev.me \
    --cc=tariqt@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 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.