From: patchwork-bot+netdevbpf@kernel.org
To: Kohei Enju <enjuk@amazon.com>
Cc: netdev@vger.kernel.org, shayagr@amazon.com, akiyano@amazon.com,
darinzon@amazon.com, saeedb@amazon.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, rosenp@gmail.com, sameehj@amazon.com,
kohei.enju@gmail.com
Subject: Re: [PATCH net v1] net: ena: return 0 in ena_get_rxfh_key_size() when RSS hash key is not configurable
Date: Tue, 30 Sep 2025 01:50:07 +0000 [thread overview]
Message-ID: <175919700725.1783832.7344252741569020332.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250929050247.51680-1-enjuk@amazon.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 29 Sep 2025 14:02:22 +0900 you wrote:
> In EC2 instances where the RSS hash key is not configurable, ethtool
> shows bogus RSS hash key since ena_get_rxfh_key_size() unconditionally
> returns ENA_HASH_KEY_SIZE.
>
> Commit 6a4f7dc82d1e ("net: ena: rss: do not allocate key when not
> supported") added proper handling for devices that don't support RSS
> hash key configuration, but ena_get_rxfh_key_size() has been unchanged.
>
> [...]
Here is the summary with links:
- [net,v1] net: ena: return 0 in ena_get_rxfh_key_size() when RSS hash key is not configurable
https://git.kernel.org/netdev/net/c/f017156aea60
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-09-30 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 5:02 [PATCH net v1] net: ena: return 0 in ena_get_rxfh_key_size() when RSS hash key is not configurable Kohei Enju
2025-09-30 1:50 ` 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=175919700725.1783832.7344252741569020332.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjuk@amazon.com \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.com \
--cc=saeedb@amazon.com \
--cc=sameehj@amazon.com \
--cc=shayagr@amazon.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.