From: Simon Horman <horms@kernel•org>
To: Takashi Kozu <takkozu@amazon•com>
Cc: anthony.l.nguyen@intel•com, przemyslaw.kitszel@intel•com,
andrew+netdev@lunn•ch, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com,
intel-wired-lan@lists•osuosl.org, netdev@vger•kernel.org,
aleksandr.loktionov@intel•com, pmenzel@molgen•mpg.de,
piotr.kwapulinski@intel•com, enjuk@amazon•com
Subject: Re: [PATCH iwl-next v5 0/3] igb: add RSS key get/set support
Date: Mon, 2 Feb 2026 10:29:38 +0000 [thread overview]
Message-ID: <aYB8ki7Yd468N_Ah@horms.kernel.org> (raw)
In-Reply-To: <20260127085410.79645-5-takkozu@amazon.com>
On Tue, Jan 27, 2026 at 05:54:07PM +0900, Takashi Kozu wrote:
> This series adds ethtool get/set support for the RSS hash key in the igb
> driver.
> - `ethtool -x <dev>` to display the RSS key
> - `ethtool -X <dev> hkey <key>` to configure the RSS key
...
Thanks,
The AI review automation did flag a typo in patch 3/3,
which I have released in the form of a response to that patch.
That notwithstanding, overall this series looks good to me.
Reviewed-by: Simon Horman <horms@kernel•org>
prev parent reply other threads:[~2026-02-02 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:54 [PATCH iwl-next v5 0/3] igb: add RSS key get/set support Takashi Kozu
2026-01-27 8:54 ` [PATCH iwl-next v5 1/3] igb: prepare for " Takashi Kozu
2026-01-27 8:54 ` [PATCH iwl-next v5 2/3] igb: expose RSS key via ethtool get_rxfh Takashi Kozu
2026-01-27 8:54 ` [PATCH iwl-next v5 3/3] igb: allow configuring RSS key via ethtool set_rxfh Takashi Kozu
2026-01-28 7:27 ` Kohei Enju
2026-02-02 10:25 ` [iwl-next,v5,3/3] " Simon Horman
2026-02-03 12:31 ` [Intel-wired-lan] [iwl-next, v5, 3/3] " Takashi Kozu
2026-02-02 10:29 ` Simon Horman [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=aYB8ki7Yd468N_Ah@horms.kernel.org \
--to=horms@kernel$(echo .)org \
--cc=aleksandr.loktionov@intel$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=enjuk@amazon$(echo .)com \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=piotr.kwapulinski@intel$(echo .)com \
--cc=pmenzel@molgen$(echo .)mpg.de \
--cc=przemyslaw.kitszel@intel$(echo .)com \
--cc=takkozu@amazon$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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