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: marcin.s.wojtas@gmail.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, linux@armlinux.org.uk, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next 0/2] net: marvell: modernize RX ring count ethtool callbacks
Date: Tue, 25 Nov 2025 03:50:10 +0000	[thread overview]
Message-ID: <176404261074.179191.13412681505599411375.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251121-marvell-v1-0-8338f3e55a4c@debian.org>

Hello:

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

On Fri, 21 Nov 2025 09:02:34 -0800 you wrote:
> This series converts the Marvell mvneta and mvpp2 drivers to use the new
> .get_rx_ring_count ethtool operation, following the ongoing modernization
> of the ethtool API introduced in commit 84eaf4359c36 ("net: ethtool: add
> get_rx_ring_count callback to optimize RX ring queries").
> 
> The conversion simplifies the code by replacing the generic .get_rxnfc
> callback with the more specific .get_rx_ring_count callback for retrieving
> RX ring counts. For mvneta, this completely removes .get_rxnfc since it
> only handled ETHTOOL_GRXRINGS. For mvpp2, the GRXRINGS case is extracted
> while keeping other rxnfc handlers intact.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] net: mvneta: convert to use .get_rx_ring_count
    https://git.kernel.org/netdev/net-next/c/737e14c5dce3
  - [net-next,2/2] net: mvpp2: extract GRXRINGS from .get_rxnfc
    https://git.kernel.org/netdev/net-next/c/20c20f05cf50

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-25  3:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 17:02 Breno Leitao
2025-11-21 17:02 ` [PATCH net-next 1/2] net: mvneta: convert to use .get_rx_ring_count Breno Leitao
2025-11-21 17:02 ` [PATCH net-next 2/2] net: mvpp2: extract GRXRINGS from .get_rxnfc Breno Leitao
2025-11-25  3: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=176404261074.179191.13412681505599411375.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=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marcin.s.wojtas@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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®