All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: tariqt@nvidia.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	saeedm@nvidia.com, mbloch@nvidia.com, leon@kernel.org,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH 0/2] net: mlx: migrate to new get_rx_ring_count ethtool API
Date: Tue, 18 Nov 2025 01:00:11 +0000	[thread overview]
Message-ID: <176342761151.3532963.1333019747310925631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251113-mlx_grxrings-v1-0-0017f2af7dd0@debian.org>

Hello:

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

On Thu, 13 Nov 2025 08:46:02 -0800 you wrote:
> This series migrates the mlx4 and mlx5 drivers to use the new
> .get_rx_ring_count() callback introduced in commit 84eaf4359c36 ("net:
> ethtool: add get_rx_ring_count callback to optimize RX ring queries").
> 
> Previously, these drivers handled ETHTOOL_GRXRINGS within the
> .get_rxnfc() callback. With the dedicated .get_rx_ring_count() API, this
> handling can be extracted and simplified.
> 
> [...]

Here is the summary with links:
  - [1/2] mlx4: extract GRXRINGS from .get_rxnfc
    https://git.kernel.org/netdev/net-next/c/467c3f008d0c
  - [2/2] mlx5: extract GRXRINGS from .get_rxnfc
    https://git.kernel.org/netdev/net-next/c/945499665f63

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



      parent reply	other threads:[~2025-11-18  1:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 16:46 [PATCH 0/2] net: mlx: migrate to new get_rx_ring_count ethtool API Breno Leitao
2025-11-13 16:46 ` [PATCH 1/2] mlx4: extract GRXRINGS from .get_rxnfc Breno Leitao
2025-11-17 12:31   ` Tariq Toukan
2025-11-13 16:46 ` [PATCH 2/2] mlx5: " Breno Leitao
2025-11-17 13:41   ` Tariq Toukan
2025-11-13 16:48 ` [PATCH 0/2] net: mlx: migrate to new get_rx_ring_count ethtool API Breno Leitao
2025-11-14  0:35   ` Jakub Kicinski
2025-11-18  1:00 ` 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=176342761151.3532963.1333019747310925631.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=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --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.