From: Jakub Kicinski <kuba@kernel.org>
To: Joshua Washington <joshwash@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, stable@kernel.org,
Praveen Kaligineedi <pkaligineedi@google.com>,
Harshitha Ramamurthy <hramamurthy@google.com>,
Willem de Bruijn <willemb@google.com>,
Eric Dumazet <edumazet@google.com>,
Andrei Vagin <avagin@gmail.com>,
Jeroen de Borst <jeroendb@google.com>,
Shailend Chand <shailend@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Rushil Gupta <rushilg@google.com>,
Catherine Sullivan <csully@google.com>,
Bailey Forrest <bcf@google.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v3] gve: ignore nonrelevant GSO type bits when processing TSO headers
Date: Mon, 10 Jun 2024 19:35:35 -0700 [thread overview]
Message-ID: <20240610193535.31fcef71@kernel.org> (raw)
In-Reply-To: <CALuQH+UtX2xqDCghHqPBckzC4k-GGi58NmOd4FNfeqOr+C4jWw@mail.gmail.com>
On Mon, 10 Jun 2024 19:26:32 -0700 Joshua Washington wrote:
> My apologies. I'll send an updated patch tomorrow without --in-reply-to.
No need, it's still in patchwork, it was just a note for the future.
I should have made that more clear, I realized that after hitting send.
next prev parent reply other threads:[~2024-06-11 2:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 19:21 [PATCH net] gve: ignore nonrelevant GSO type bits when processing TSO headers joshwash
2024-06-06 21:53 ` Willem de Bruijn
2024-06-06 22:16 ` Andrei Vagin
2024-06-07 6:09 ` [PATCH net v2] " joshwash
2024-06-07 6:35 ` Eric Dumazet
2024-06-07 14:07 ` Willem de Bruijn
2024-06-10 22:57 ` [PATCH net v3] " joshwash
2024-06-11 0:27 ` Jakub Kicinski
2024-06-11 2:26 ` Joshua Washington
2024-06-11 2:35 ` Jakub Kicinski [this message]
2024-06-12 3:00 ` patchwork-bot+netdevbpf
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=20240610193535.31fcef71@kernel.org \
--to=kuba@kernel.org \
--cc=avagin@gmail.com \
--cc=bcf@google.com \
--cc=csully@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=stable@kernel.org \
--cc=willemb@google.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).