From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shayagr@amazon.com, akiyano@amazon.com, darinzon@amazon.com,
skalluru@marvell.com, manishc@marvell.com,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, bbhushan2@marvell.com
Subject: Re: [PATCH net-next 0/5] eth: migrate some drivers to new RXFH callbacks
Date: Wed, 18 Jun 2025 20:30:22 +0000 [thread overview]
Message-ID: <175027862274.246778.380508616545971353.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250617014555.434790-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Jun 2025 18:45:50 -0700 you wrote:
> Migrate a batch of drivers to the recently added dedicated
> .get_rxfh_fields and .set_rxfh_fields ethtool callbacks.
>
> Jakub Kicinski (5):
> eth: bnx2x: migrate to new RXFH callbacks
> eth: bnxt: migrate to new RXFH callbacks
> eth: ena: migrate to new RXFH callbacks
> eth: thunder: migrate to new RXFH callbacks
> eth: otx2: migrate to new RXFH callbacks
>
> [...]
Here is the summary with links:
- [net-next,1/5] eth: bnx2x: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/f1a6fcc454dd
- [net-next,2/5] eth: bnxt: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/82113468a088
- [net-next,3/5] eth: ena: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/e7860a6e1826
- [net-next,4/5] eth: thunder: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/e8b87384391b
- [net-next,5/5] eth: otx2: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/f99ff3c2a328
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-18 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 1:45 [PATCH net-next 0/5] eth: migrate some drivers to new RXFH callbacks Jakub Kicinski
2025-06-17 1:45 ` [PATCH net-next 1/5] eth: bnx2x: migrate " Jakub Kicinski
2025-06-17 6:40 ` Subbaraya Sundeep
2025-06-17 22:14 ` Jakub Kicinski
2025-06-18 10:03 ` Subbaraya Sundeep
2025-06-17 1:45 ` [PATCH net-next 2/5] eth: bnxt: " Jakub Kicinski
2025-06-17 21:39 ` Michael Chan
2025-06-17 1:45 ` [PATCH net-next 3/5] eth: ena: " Jakub Kicinski
2025-06-17 6:50 ` Subbaraya Sundeep
2025-06-17 7:35 ` Arinzon, David
2025-06-17 1:45 ` [PATCH net-next 4/5] eth: thunder: " Jakub Kicinski
2025-06-17 6:43 ` Subbaraya Sundeep
2025-06-17 1:45 ` [PATCH net-next 5/5] eth: otx2: " Jakub Kicinski
2025-06-18 20: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=175027862274.246778.380508616545971353.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=shayagr@amazon.com \
--cc=skalluru@marvell.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.