From: Michal Kubiak <michal.kubiak@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Ignat Korchagin <ignat@cloudflare.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-team@cloudflare.com>
Subject: Re: [PATCH net v2 2/2] selftests: net: veth: test the ability to independently manipulate GRO and XDP
Date: Wed, 13 Mar 2024 15:03:16 +0100 [thread overview]
Message-ID: <ZfGyJMSWbZCqqFlM@localhost.localdomain> (raw)
In-Reply-To: <20240313065725.46a50ea8@kernel.org>
On Wed, Mar 13, 2024 at 06:57:25AM -0700, Jakub Kicinski wrote:
> On Wed, 13 Mar 2024 12:28:41 +0100 Michal Kubiak wrote:
> > On Tue, Mar 12, 2024 at 04:05:52PM +0000, Ignat Korchagin wrote:
> > > We should be able to independently flip either XDP or GRO states and toggling
> > > one should not affect the other.
> > >
> > > Signed-off-by: Ignat Korchagin <ignat@cloudflare.com>
> >
> > Missing "Fixes" tag for the patch targeted to the "net" tree.
>
> it's adjusting a selftest, I don't think we need a Fixes tag for that
OK, sorry! My mistake, then.
Michal
next prev parent reply other threads:[~2024-03-13 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 16:05 [PATCH net v2 0/2] net: veth: ability to toggle GRO and XDP independently Ignat Korchagin
2024-03-12 16:05 ` [PATCH net v2 1/2] net: veth: do not manipulate GRO when using XDP Ignat Korchagin
2024-03-12 16:05 ` [PATCH net v2 2/2] selftests: net: veth: test the ability to independently manipulate GRO and XDP Ignat Korchagin
2024-03-13 11:28 ` Michal Kubiak
2024-03-13 13:57 ` Jakub Kicinski
2024-03-13 14:03 ` Michal Kubiak [this message]
2024-03-13 14:09 ` Jakub Kicinski
2024-03-12 23:42 ` [PATCH net v2 0/2] net: veth: ability to toggle GRO and XDP independently Jakub Kicinski
2024-03-13 18:40 ` Ignat Korchagin
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=ZfGyJMSWbZCqqFlM@localhost.localdomain \
--to=michal.kubiak@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ignat@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).