From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Tariq Toukan <tariqt@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>, Leon Romanovsky <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: Thu, 13 Nov 2025 16:35:11 -0800 [thread overview]
Message-ID: <20251113163511.50626066@kernel.org> (raw)
In-Reply-To: <lto3b6lf2ic6ajph74ljo2ibpmoltkgpswfbvcprx5pr3iqfoi@67u4olbyq4km>
On Thu, 13 Nov 2025 08:48:20 -0800 Breno Leitao wrote:
> On Thu, Nov 13, 2025 at 08:46:02AM -0800, Breno Leitao 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").
>
> This is "net-next" material. I will update and resend with the proper
> "net-next" tag.
No need to repost. net-next is the default
next prev parent reply other threads:[~2025-11-14 0:35 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 [this message]
2025-11-18 1:00 ` patchwork-bot+netdevbpf
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=20251113163511.50626066@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--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.