From: Jakub Kicinski <kuba@kernel.org>
To: "Chuck Lever" <cel@kernel.org>
Cc: john.fastabend@gmail.com, "Sabrina Dubroca" <sd@queasysnail.net>,
netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
"Chuck Lever" <chuck.lever@oracle.com>,
"Hannes Reinecke" <hare@suse.de>,
"Alistair Francis" <alistair.francis@wdc.com>
Subject: Re: [PATCH net-next v7 0/5] TLS read_sock performance scalability
Date: Sun, 26 Apr 2026 16:55:51 -0700 [thread overview]
Message-ID: <20260426165551.43321865@kernel.org> (raw)
In-Reply-To: <4a802e09-d1af-4af3-8f02-3e2c8d25e734@app.fastmail.com>
On Sat, 25 Apr 2026 16:15:41 -0400 Chuck Lever wrote:
> On Wed, Apr 22, 2026, at 10:08 PM, Jakub Kicinski wrote:
> > On Wed, 22 Apr 2026 12:41:43 -0400 Chuck Lever wrote:
> >> I see that this series is currently not in v7.1. What is left to do?
> >
> > It's marked as Changes requested in patchwork, possibly due to
> > mis-reading of the discussion on patch 4. We process patches within
> > few days (well, we used to before the AI swarm) so if in doubt you
> > should ask sooner :S
>
> Thanks for the pointer to the netdevbpf patchworks instance. Anything
> I can do to move this series to "Awaiting upsteam" ?
Repost after net-next reopens
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
prev parent reply other threads:[~2026-04-26 23:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 15:17 [PATCH net-next v7 0/5] TLS read_sock performance scalability Chuck Lever
2026-03-28 15:17 ` [PATCH net-next v7 1/5] tls: Abort the connection on decrypt failure Chuck Lever
2026-03-28 15:17 ` [PATCH net-next v7 2/5] tls: Fix dangling skb pointer in tls_sw_read_sock() Chuck Lever
2026-03-30 12:17 ` Sabrina Dubroca
2026-03-28 15:17 ` [PATCH net-next v7 3/5] tls: Factor tls_strp_msg_release() from tls_strp_msg_done() Chuck Lever
2026-03-30 12:21 ` Sabrina Dubroca
2026-03-28 15:17 ` [PATCH net-next v7 4/5] tls: Suppress spurious saved_data_ready on all receive paths Chuck Lever
2026-03-30 14:43 ` Sabrina Dubroca
2026-03-31 2:06 ` Chuck Lever
2026-03-28 15:17 ` [PATCH net-next v7 5/5] tls: Flush backlog before waiting for a new record Chuck Lever
2026-04-22 16:41 ` [PATCH net-next v7 0/5] TLS read_sock performance scalability Chuck Lever
2026-04-23 2:08 ` Jakub Kicinski
2026-04-25 20:15 ` Chuck Lever
2026-04-26 23:55 ` Jakub Kicinski [this message]
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=20260426165551.43321865@kernel.org \
--to=kuba@kernel.org \
--cc=alistair.francis@wdc.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hare@suse.de \
--cc=john.fastabend@gmail.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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.