From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH net-next 0/2] bnxt_en: Add RSS context resource check
Date: Wed, 11 Feb 2026 04:30:07 +0000 [thread overview]
Message-ID: <177078420783.4194295.3293083983118159892.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260207235118.1987301-1-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 7 Feb 2026 15:51:16 -0800 you wrote:
> Add missing logic to check that we have enough RSS contexts. This
> will make the recent change to increase the use of RSS contexts for
> a larger RSS indirection table more complete.
>
> Michael Chan (2):
> bnxt_en: Refactor bnxt_need_reserve_rings()
> bnxt_en: Check RSS contexts in bnxt_need_reserve_rings()
>
> [...]
Here is the summary with links:
- [net-next,1/2] bnxt_en: Refactor bnxt_need_reserve_rings()
https://git.kernel.org/netdev/net-next/c/5a2f3aa2896f
- [net-next,2/2] bnxt_en: Check RSS contexts in bnxt_need_reserve_rings()
https://git.kernel.org/netdev/net-next/c/b9355ad52b38
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:[~2026-02-11 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 23:51 [PATCH net-next 0/2] bnxt_en: Add RSS context resource check Michael Chan
2026-02-07 23:51 ` [PATCH net-next 1/2] bnxt_en: Refactor bnxt_need_reserve_rings() Michael Chan
2026-02-09 22:21 ` Joe Damato
2026-02-07 23:51 ` [PATCH net-next 2/2] bnxt_en: Check RSS contexts in bnxt_need_reserve_rings() Michael Chan
2026-02-09 22:22 ` Joe Damato
2026-02-11 4: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=177078420783.4194295.3293083983118159892.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--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 \
/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