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, michael.chan@broadcom.com, shuah@kernel.org,
ecree.xilinx@gmail.com, przemyslaw.kitszel@intel.com,
ahmed.zaki@intel.com, andrew@lunn.ch, willemb@google.com,
pavan.chebbi@broadcom.com, petrm@nvidia.com
Subject: Re: [PATCH net 0/5] ethtool: more RSS fixes
Date: Mon, 29 Jul 2024 10:08:06 +0000 [thread overview]
Message-ID: <172224768647.24246.8753503956784144711.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240725222353.2993687-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 25 Jul 2024 15:23:48 -0700 you wrote:
> More fixes for RSS setting. First two patches fix my own bugs
> in bnxt conversion to the new API. The third patch fixes
> what seems to be a 10 year old issue (present since the Linux
> RSS API was created). Fourth patch fixes an issue with
> the XArray state being out of sync. And then a small test.
>
> Jakub Kicinski (5):
> eth: bnxt: reject unsupported hash functions
> eth: bnxt: populate defaults in the RSS context struct
> ethtool: fix setting key and resetting indir at once
> ethtool: fix the state of additional contexts with old API
> selftests: drv-net: rss_ctx: check for all-zero keys
>
> [...]
Here is the summary with links:
- [net,1/5] eth: bnxt: reject unsupported hash functions
https://git.kernel.org/netdev/net/c/daefd348a593
- [net,2/5] eth: bnxt: populate defaults in the RSS context struct
https://git.kernel.org/netdev/net/c/9dbad38336a9
- [net,3/5] ethtool: fix setting key and resetting indir at once
https://git.kernel.org/netdev/net/c/7195f0ef7f5b
- [net,4/5] ethtool: fix the state of additional contexts with old API
https://git.kernel.org/netdev/net/c/dc9755370e1c
- [net,5/5] selftests: drv-net: rss_ctx: check for all-zero keys
https://git.kernel.org/netdev/net/c/0d6ccfe6b319
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:[~2024-07-29 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 22:23 [PATCH net 0/5] ethtool: more RSS fixes Jakub Kicinski
2024-07-25 22:23 ` [PATCH net 1/5] eth: bnxt: reject unsupported hash functions Jakub Kicinski
2024-07-26 6:16 ` Pavan Chebbi
2024-07-25 22:23 ` [PATCH net 2/5] eth: bnxt: populate defaults in the RSS context struct Jakub Kicinski
2024-07-26 6:15 ` Pavan Chebbi
2024-07-25 22:23 ` [PATCH net 3/5] ethtool: fix setting key and resetting indir at once Jakub Kicinski
2024-07-25 22:23 ` [PATCH net 4/5] ethtool: fix the state of additional contexts with old API Jakub Kicinski
2024-07-26 5:06 ` Edward Cree
2024-07-25 22:23 ` [PATCH net 5/5] selftests: drv-net: rss_ctx: check for all-zero keys Jakub Kicinski
2024-07-26 11:25 ` Petr Machata
2024-07-29 10:08 ` 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=172224768647.24246.8753503956784144711.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=petrm@nvidia.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shuah@kernel.org \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).