[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250915144651.7bec7ad4@kernel.org>
Date: Mon, 15 Sep 2025 14:46:51 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Keith Busch <kbusch@...nel.org>
Cc: Olga Kornievskaia <aglo@...ch.edu>, Olga Kornievskaia
<okorniev@...hat.com>, chuck.lever@...cle.com, jlayton@...nel.org,
trondmy@...merspace.com, anna.schumaker@...cle.com, hch@....de,
sagi@...mberg.me, kch@...dia.com, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, linux-nfs@...r.kernel.org,
linux-nvme@...ts.infradead.org, netdev@...r.kernel.org,
kernel-tls-handshake@...ts.linux.dev, neil@...wn.name, Dai.Ngo@...cle.com,
tom@...pey.com, hare@...e.de, horms@...nel.org
Subject: Re: [PATCH v2 3/4] nvmet-tcp: fix handling of tls alerts
On Mon, 15 Sep 2025 09:45:16 -0600 Keith Busch wrote:
> On Fri, Sep 05, 2025 at 12:10:21PM -0400, Olga Kornievskaia wrote:
> > Dear NvME maintainers,
> >
> > Are there objections to this patch? What's the path forward to
> > including it in the nvme code.
>
> Sorry for the delay here. This series is mostly outside the nvme driver,
> so we need at least need an Ack from the networking folks if we're going
> to take this through the nvme tree.
In case you decide to take it, LGTM:
Acked-by: Jakub Kicinski <kuba@...nel.org>
Thanks!
Powered by blists - more mailing lists