mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, kuba@kernel.org, horms@kernel.org,
	mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
	eperezma@redhat.com, andrew+netdev@lunn.ch,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux.dev, leiyang@redhat.com,
	kernel-team@meta.com
Subject: Re: [PATCH net-next v4 0/8] net: ethtool: add dedicated GRXRINGS driver callbacks
Date: Thu, 18 Sep 2025 14:30:18 +0000	[thread overview]
Message-ID: <175820581800.2438890.5576765054312020810.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250917-gxrings-v4-0-dae520e2e1cb@debian.org>

Hello:

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

On Wed, 17 Sep 2025 02:58:07 -0700 you wrote:
> This patchset introduces a new dedicated ethtool_ops callback,
> .get_rx_ring_count, which enables drivers to provide the number of RX
> rings directly, improving efficiency and clarity in RX ring queries and
> RSS configuration.
> 
> Number of drivers implements .get_rxnfc callback just to report the ring
> count, so, having a proper callback makes sense and simplify .get_rxnfc
> (in some cases remove it completely).
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/8] net: ethtool: pass the num of RX rings directly to ethtool_copy_validate_indir
    https://git.kernel.org/netdev/net-next/c/3efaede2e13b
  - [net-next,v4,2/8] net: ethtool: add support for ETHTOOL_GRXRINGS ioctl
    https://git.kernel.org/netdev/net-next/c/06fad5a4aeb2
  - [net-next,v4,3/8] net: ethtool: remove the duplicated handling from ethtool_get_rxrings
    https://git.kernel.org/netdev/net-next/c/87c76c2db002
  - [net-next,v4,4/8] net: ethtool: add get_rx_ring_count callback to optimize RX ring queries
    https://git.kernel.org/netdev/net-next/c/84eaf4359c36
  - [net-next,v4,5/8] net: ethtool: update set_rxfh to use ethtool_get_rx_ring_count helper
    https://git.kernel.org/netdev/net-next/c/d5544688d421
  - [net-next,v4,6/8] net: ethtool: update set_rxfh_indir to use ethtool_get_rx_ring_count helper
    https://git.kernel.org/netdev/net-next/c/dce08107f1f3
  - [net-next,v4,7/8] net: ethtool: use the new helper in rss_set_prep_indir()
    https://git.kernel.org/netdev/net-next/c/8b7c4b612dec
  - [net-next,v4,8/8] net: virtio_net: add get_rxrings ethtool callback for RX ring queries
    https://git.kernel.org/netdev/net-next/c/483446690a62

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-09-18 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  9:58 Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 1/8] net: ethtool: pass the num of RX rings directly to ethtool_copy_validate_indir Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 2/8] net: ethtool: add support for ETHTOOL_GRXRINGS ioctl Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 3/8] net: ethtool: remove the duplicated handling from ethtool_get_rxrings Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 4/8] net: ethtool: add get_rx_ring_count callback to optimize RX ring queries Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 5/8] net: ethtool: update set_rxfh to use ethtool_get_rx_ring_count helper Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 6/8] net: ethtool: update set_rxfh_indir " Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 7/8] net: ethtool: use the new helper in rss_set_prep_indir() Breno Leitao
2025-09-17  9:58 ` [PATCH net-next v4 8/8] net: virtio_net: add get_rxrings ethtool callback for RX ring queries Breno Leitao
2025-09-18 14: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=175820581800.2438890.5576765054312020810.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=horms@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=leiyang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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

all inboxes | Powered by JetHome®