From: Christoph Hellwig <hch@lst.de>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, kbusch@kernel.org,
sagi@grimberg.me, hare@suse.de, mlombard@bsdbackstore.eu
Subject: Re: [PATCH V2] nvme-tcp: log TLS handshake failures at error level
Date: Thu, 3 Jul 2025 13:43:38 +0200 [thread overview]
Message-ID: <20250703114338.GA17686@lst.de> (raw)
In-Reply-To: <20250702140629.70378-1-mlombard@redhat.com>
Thanks, applied to nvme-6.17.
prev parent reply other threads:[~2025-07-03 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 14:06 [PATCH V2] nvme-tcp: log TLS handshake failures at error level Maurizio Lombardi
2025-07-02 16:17 ` Hannes Reinecke
2025-07-02 18:17 ` Laurence Oberman
2025-07-03 11:43 ` Christoph Hellwig [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=20250703114338.GA17686@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@bsdbackstore.eu \
--cc=mlombard@redhat.com \
--cc=sagi@grimberg.me \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).