All of lore.kernel.org
 help / color / mirror / Atom feed
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, pavan.chebbi@broadcom.com,
	andrew.gospodarek@broadcom.com
Subject: Re: [PATCH] bnxt_en: Fix RSS logic in __bnxt_reserve_rings()
Date: Thu, 25 Jul 2024 23:30:33 +0000	[thread overview]
Message-ID: <172195023315.25262.12343985900887431574.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240724222106.147744-1-michael.chan@broadcom.com>

Hello:

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

On Wed, 24 Jul 2024 15:21:06 -0700 you wrote:
> From: Pavan Chebbi <pavan.chebbi@broadcom.com>
> 
> In __bnxt_reserve_rings(), the existing code unconditionally sets the
> default RSS indirection table to default if netif_is_rxfh_configured()
> returns false.  This used to be correct before we added RSS contexts
> support.  For example, if the user is changing the number of ethtool
> channels, we will enter this path to reserve the new number of rings.
> We will then set the RSS indirection table to default to cover the new
> number of rings if netif_is_rxfh_configured() is false.
> 
> [...]

Here is the summary with links:
  - bnxt_en: Fix RSS logic in __bnxt_reserve_rings()
    https://git.kernel.org/netdev/net/c/98ba1d931f61

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-07-25 23:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 22:21 [PATCH] bnxt_en: Fix RSS logic in __bnxt_reserve_rings() Michael Chan
2024-07-25  0:25 ` Jakub Kicinski
2024-07-25 18:19   ` Jakub Kicinski
2024-07-25 21:33     ` Andy Gospodarek
2024-07-25 22:32       ` Jakub Kicinski
2024-07-26  6:23         ` Pavan Chebbi
2024-07-25 23: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=172195023315.25262.12343985900887431574.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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 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.