[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <40c707d6-db49-40a8-8372-7c3a91c2ff5f@suse.de>
Date: Tue, 16 Sep 2025 13:28:31 +0200
From: Hannes Reinecke <hare@...e.de>
To: Jakub Kicinski <kuba@...nel.org>, 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, horms@...nel.org
Subject: Re: [PATCH v2 3/4] nvmet-tcp: fix handling of tls alerts
On 9/15/25 23:46, Jakub Kicinski wrote:
> 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!
>
Okay, after further thinking I would vote for the
NVMe tree after all. There are more patches queued
up which will require these changes, and life will
be easier if we had just one branch where we could
base them on.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
Powered by blists - more mailing lists