From: Jakub Kicinski <kuba@kernel.org>
To: Keith Busch <kbusch@kernel.org>
Cc: Olga Kornievskaia <aglo@umich.edu>,
Olga Kornievskaia <okorniev@redhat.com>,
chuck.lever@oracle.com, jlayton@kernel.org,
trondmy@hammerspace.com, anna.schumaker@oracle.com, hch@lst.de,
sagi@grimberg.me, kch@nvidia.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
linux-nfs@vger.kernel.org, linux-nvme@lists.infradead.org,
netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
neil@brown.name, Dai.Ngo@oracle.com, tom@talpey.com,
hare@suse.de, horms@kernel.org
Subject: Re: [PATCH v2 3/4] nvmet-tcp: fix handling of tls alerts
Date: Mon, 15 Sep 2025 14:46:51 -0700 [thread overview]
Message-ID: <20250915144651.7bec7ad4@kernel.org> (raw)
In-Reply-To: <aMg0jDkXOd8E7Ihj@kbusch-mbp>
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@kernel.org>
Thanks!
next prev parent reply other threads:[~2025-09-15 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 18:00 [PATCH v2 0/4] address tls_alert_recv usage by NFS and NvME Olga Kornievskaia
2025-07-31 18:00 ` [PATCH v2 1/4] sunrpc: fix handling of server side tls alerts Olga Kornievskaia
2025-07-31 18:00 ` [PATCH v2 2/4] sunrpc: fix client side handling of " Olga Kornievskaia
2025-07-31 18:00 ` [PATCH v2 3/4] nvmet-tcp: fix " Olga Kornievskaia
2025-09-05 16:10 ` Olga Kornievskaia
2025-09-15 15:45 ` Keith Busch
2025-09-15 15:55 ` Hannes Reinecke
2025-09-15 21:46 ` Jakub Kicinski [this message]
2025-09-16 11:28 ` Hannes Reinecke
2025-07-31 18:00 ` [PATCH v2 4/4] net/handshake: change tls_alert_recv to receive a kvec Olga Kornievskaia
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=20250915144651.7bec7ad4@kernel.org \
--to=kuba@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=aglo@umich.edu \
--cc=anna.schumaker@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=horms@kernel.org \
--cc=jlayton@kernel.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=pabeni@redhat.com \
--cc=sagi@grimberg.me \
--cc=tom@talpey.com \
--cc=trondmy@hammerspace.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 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.