From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Takeru Hayasaka <hayatake396@gmail.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, vladimir.oltean@nxp.com,
linux-kernel@vger.kernel.org, laforge@gnumonks.org,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
mailhol.vincent@wanadoo.fr
Subject: Re: [Intel-wired-lan] [PATCH net-next v3] ethtool: ice: Support for RSS settings to GTP from ethtool
Date: Fri, 26 Jan 2024 12:12:32 +0100 [thread overview]
Message-ID: <fb90ae9c-1f83-424c-878a-8b7e472bb6f0@molgen.mpg.de> (raw)
In-Reply-To: <20240126045220.861125-1-hayatake396@gmail.com>
Dear Takeru,
This patch was sent at least four(?) times to the mailing list. Could
you please sent a patch tagged with [RESENT] or a v4, so there won’t be
several replies to different threads.
One nit below:
Am 26.01.24 um 05:52 schrieb Takeru Hayasaka:
> This is a patch that enables RSS functionality for GTP packets using
> ethtool.
> A user can include her TEID and make RSS work for GTP-U over IPv4 by
> doing the following:
> `ethtool -N ens3 rx-flow-hash gtpu4 sde`
> In addition to gtpu(4|6), we now support gtpc(4|6),gtpc(4|6)t,gtpu(4|6)e,
> gtpu(4|6)u, and gtpu(4|6)d.
Should you sent another iteration, please do not break lines, just
because a sentence ends, and please add a blank line between paragraphs.
[…]
Kind regards,
Paul
next prev parent reply other threads:[~2024-01-26 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 4:52 [PATCH net-next v3] ethtool: ice: Support for RSS settings to GTP from ethtool Takeru Hayasaka
2024-01-26 11:12 ` Paul Menzel [this message]
2024-01-27 11:10 ` [Intel-wired-lan] " takeru hayasaka
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=fb90ae9c-1f83-424c-878a-8b7e472bb6f0@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayatake396@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).