From: Jakub Kicinski <kuba@kernel•org>
To: Xin Long <lucien.xin@gmail•com>
Cc: network dev <netdev@vger•kernel.org>,
quic@lists•linux.dev, davem@davemloft•net,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>, Simon Horman <horms@kernel•org>,
Stefan Metzmacher <metze@samba•org>,
Moritz Buhl <mbuhl@openbsd•org>,
Tyler Fanelli <tfanelli@redhat•com>,
Pengtao He <hepengtao@xiaomi•com>,
Thomas Dreibholz <dreibh@simula•no>,
linux-cifs@vger•kernel.org, Steve French <smfrench@gmail•com>,
Namjae Jeon <linkinjeon@kernel•org>,
Paulo Alcantara <pc@manguebit•com>, Tom Talpey <tom@talpey•com>,
kernel-tls-handshake@lists•linux.dev,
Chuck Lever <chuck.lever@oracle•com>,
Jeff Layton <jlayton@kernel•org>,
Steve Dickson <steved@redhat•com>, Hannes Reinecke <hare@suse•de>,
Alexander Aring <aahringo@redhat•com>,
David Howells <dhowells@redhat•com>,
Matthieu Baerts <matttbe@kernel•org>,
John Ericson <mail@johnericson•me>,
Cong Wang <xiyou.wangcong@gmail•com>,
"D . Wythe" <alibuda@linux•alibaba.com>,
Jason Baron <jbaron@akamai•com>,
illiliti <illiliti@protonmail•com>,
Sabrina Dubroca <sd@queasysnail•net>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail•com>,
Daniel Stenberg <daniel@haxx•se>,
Andy Gospodarek <andrew.gospodarek@broadcom•com>,
"Marc E . Fiuczynski" <marc@fiuczynski•com>
Subject: Re: [PATCH net-next v11 06/15] quic: add stream management
Date: Thu, 26 Mar 2026 18:00:01 -0700 [thread overview]
Message-ID: <20260326180001.793b62be@kernel.org> (raw)
In-Reply-To: <CADvbK_eyNtAfA=JPR5Y4arFLPpkWMs8io=TO83rHAa-JJkhdAA@mail.gmail.com>
On Thu, 26 Mar 2026 17:48:51 -0400 Xin Long wrote:
> > Can you also check the google one?
> >
> > https://sashiko.dev/#/patchset/4019cfba3ffd6f91aee24713d2adc778f858b4c4.1774410440.git.lucien.xin@gmail.com
>
> Will do. There are quite a few reports, and it may take me some time
> to review them all carefully.
>
> BTW, what's the workflow for the Google AI feedback? should I reply to
> each item in this thread like we did with Claude one, or is there a
> different workflow?
It's a bit more chatty and we don't have any integrations there so it's
a bit hard to deal with :( At this point just look thru the reports and
address what's legit. We'll probably take your word for everything that
remains being a false positive.
next prev parent reply other threads:[~2026-03-27 1:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 3:47 [PATCH net-next v11 00/15] net: introduce QUIC infrastructure and core subcomponents Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 01/15] net: define IPPROTO_QUIC and SOL_QUIC constants Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 02/15] net: build socket infrastructure for QUIC protocol Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 03/15] quic: provide common utilities and data structures Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 04/15] quic: provide family ops for address and protocol Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 05/15] quic: provide quic.h header files for kernel and userspace Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 06/15] quic: add stream management Xin Long
2026-03-26 15:06 ` Xin Long
2026-03-26 20:07 ` Jakub Kicinski
2026-03-26 21:48 ` Xin Long
2026-03-27 1:00 ` Jakub Kicinski [this message]
2026-03-25 3:47 ` [PATCH net-next v11 07/15] quic: add connection id management Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 08/15] quic: add path management Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 09/15] quic: add congestion control Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 10/15] quic: add packet number space Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 11/15] quic: add crypto key derivation and installation Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 12/15] quic: add crypto packet encryption and decryption Xin Long
2026-03-26 15:10 ` Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 13/15] quic: add timer management Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 14/15] quic: add packet builder base Xin Long
2026-03-25 3:47 ` [PATCH net-next v11 15/15] quic: add packet parser base Xin Long
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=20260326180001.793b62be@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=aahringo@redhat$(echo .)com \
--cc=alibuda@linux$(echo .)alibaba.com \
--cc=andrew.gospodarek@broadcom$(echo .)com \
--cc=chuck.lever@oracle$(echo .)com \
--cc=daniel@haxx$(echo .)se \
--cc=davem@davemloft$(echo .)net \
--cc=dhowells@redhat$(echo .)com \
--cc=dreibh@simula$(echo .)no \
--cc=edumazet@google$(echo .)com \
--cc=hare@suse$(echo .)de \
--cc=hepengtao@xiaomi$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=illiliti@protonmail$(echo .)com \
--cc=jbaron@akamai$(echo .)com \
--cc=jlayton@kernel$(echo .)org \
--cc=kernel-tls-handshake@lists$(echo .)linux.dev \
--cc=linkinjeon@kernel$(echo .)org \
--cc=linux-cifs@vger$(echo .)kernel.org \
--cc=lucien.xin@gmail$(echo .)com \
--cc=mail@johnericson$(echo .)me \
--cc=marc@fiuczynski$(echo .)com \
--cc=marcelo.leitner@gmail$(echo .)com \
--cc=matttbe@kernel$(echo .)org \
--cc=mbuhl@openbsd$(echo .)org \
--cc=metze@samba$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pc@manguebit$(echo .)com \
--cc=quic@lists$(echo .)linux.dev \
--cc=sd@queasysnail$(echo .)net \
--cc=smfrench@gmail$(echo .)com \
--cc=steved@redhat$(echo .)com \
--cc=tfanelli@redhat$(echo .)com \
--cc=tom@talpey$(echo .)com \
--cc=xiyou.wangcong@gmail$(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