From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Kohei Enju <kohei@enjuk.jp>
Cc: <aleksandr.loktionov@intel.com>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <enjuk@amazon.com>,
<intel-wired-lan@lists.osuosl.org>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<piotr.kwapulinski@intel.com>, <pmenzel@molgen.mpg.de>,
<przemyslaw.kitszel@intel.com>, <takkozu@amazon.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 3/3] igb: allow configuring RSS key via
Date: Wed, 28 Jan 2026 09:33:22 -0800 [thread overview]
Message-ID: <59b428e1-dfed-4e80-be62-5c4ee4469e8a@intel.com> (raw)
In-Reply-To: <20260128060958.6333-1-kohei@enjuk.jp>
On 1/27/2026 10:09 PM, Kohei Enju wrote:
>
> Yes, you're right. I'd love to do that and post as new version,
> so could you drop the series[1] from tnguy/next-queue.git?
Done.
Thanks,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Kohei Enju <kohei@enjuk.jp>
Cc: <aleksandr.loktionov@intel.com>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <enjuk@amazon.com>,
<intel-wired-lan@lists.osuosl.org>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<piotr.kwapulinski@intel.com>, <pmenzel@molgen.mpg.de>,
<przemyslaw.kitszel@intel.com>, <takkozu@amazon.com>
Subject: Re: [PATCH iwl-next v4 3/3] igb: allow configuring RSS key via
Date: Wed, 28 Jan 2026 09:33:22 -0800 [thread overview]
Message-ID: <59b428e1-dfed-4e80-be62-5c4ee4469e8a@intel.com> (raw)
In-Reply-To: <20260128060958.6333-1-kohei@enjuk.jp>
On 1/27/2026 10:09 PM, Kohei Enju wrote:
>
> Yes, you're right. I'd love to do that and post as new version,
> so could you drop the series[1] from tnguy/next-queue.git?
Done.
Thanks,
Tony
next prev parent reply other threads:[~2026-01-28 17:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 9:34 [Intel-wired-lan] [PATCH iwl-next v4 0/3] igb: add RSS key get/set support Takashi Kozu
2026-01-20 9:34 ` Takashi Kozu
2026-01-20 9:34 ` [Intel-wired-lan] [PATCH iwl-next v4 1/3] igb: prepare for " Takashi Kozu
2026-01-20 9:34 ` Takashi Kozu
2026-01-20 9:36 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-20 9:36 ` Loktionov, Aleksandr
2026-01-20 15:26 ` [Intel-wired-lan] " Kwapulinski, Piotr
2026-01-20 15:26 ` Kwapulinski, Piotr
2026-01-20 9:34 ` [Intel-wired-lan] [PATCH iwl-next v4 2/3] igb: expose RSS key via ethtool get_rxfh Takashi Kozu
2026-01-20 9:34 ` Takashi Kozu
2026-01-20 9:34 ` [Intel-wired-lan] [PATCH iwl-next v4 3/3] igb: allow configuring RSS key via ethtool set_rxfh Takashi Kozu
2026-01-20 9:34 ` Takashi Kozu
2026-01-25 13:12 ` [Intel-wired-lan] " Kohei Enju
2026-01-25 13:12 ` Kohei Enju
2026-01-27 22:33 ` [Intel-wired-lan] " Tony Nguyen
2026-01-27 22:33 ` Tony Nguyen
2026-01-28 6:09 ` [Intel-wired-lan] [PATCH iwl-next v4 3/3] igb: allow configuring RSS key via Kohei Enju
2026-01-28 6:09 ` Kohei Enju
2026-01-28 17:33 ` Tony Nguyen [this message]
2026-01-28 17:33 ` Tony Nguyen
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=59b428e1-dfed-4e80-be62-5c4ee4469e8a@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjuk@amazon.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kohei@enjuk.jp \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piotr.kwapulinski@intel.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.com \
--cc=takkozu@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.