From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: pavan.chebbi@broadcom.com, netdev@vger.kernel.org,
kalesh-anakkur.purayil@broadcom.com,
linux-kselftest@vger.kernel.org, michael.chan@broadcom.com,
linux-kernel@vger.kernel.org, kuba@kernel.org,
martin.lau@linux.dev, ecree.xilinx@gmail.com,
kernel-team@meta.com
Subject: Re: [PATCH net v3 0/2] bnxt: Fix failure to report RSS context in ntuple rule
Date: Sat, 30 Nov 2024 22:20:30 +0000 [thread overview]
Message-ID: <173300523098.2492979.671614887548460741.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1732748253.git.dxu@dxuuu.xyz>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Nov 2024 15:58:28 -0700 you wrote:
> This patchset fixes a bug where bnxt driver was failing to report that
> an ntuple rule is redirecting to an RSS context. First commit is the
> fix, then second commit extends selftests to detect if other/new drivers
> are compliant with ntuple/rss_ctx API.
>
> === Changelog ===
>
> [...]
Here is the summary with links:
- [net,v3,1/2] bnxt_en: ethtool: Supply ntuple rss context action
https://git.kernel.org/netdev/net/c/be75cda92a65
- [net,v3,2/2] selftests: drv-net: rss_ctx: Add test for ntuple rule
https://git.kernel.org/netdev/net/c/7078d43b2374
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-11-30 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 22:58 [PATCH net v3 0/2] bnxt: Fix failure to report RSS context in ntuple rule Daniel Xu
2024-11-27 22:58 ` [PATCH net v3 1/2] bnxt_en: ethtool: Supply ntuple rss context action Daniel Xu
2024-11-27 22:58 ` [PATCH net v3 2/2] selftests: drv-net: rss_ctx: Add test for ntuple rule Daniel Xu
2024-11-30 22:20 ` 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=173300523098.2492979.671614887548460741.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=ecree.xilinx@gmail.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pavan.chebbi@broadcom.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