From: David Howells <dhowells@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: dhowells@redhat.com, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCHv6 0/5] net/tls: fixes for NVMe-over-TLS
Date: Mon, 03 Jul 2023 13:45:30 +0100 [thread overview]
Message-ID: <874611.1688388330@warthog.procyon.org.uk> (raw)
In-Reply-To: <6859f3b7-90fa-7071-857e-d9354165a445@suse.de>
Hannes Reinecke <hare@suse.de> wrote:
> msg.msg_flags &= ~MSG_SPLICE_PAGES,
Ah, yes - as Sagi pointed out there's a patch for that comma there.
David
prev parent reply other threads:[~2023-07-03 12:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 9:04 [PATCHv6 0/5] net/tls: fixes for NVMe-over-TLS Hannes Reinecke
2023-07-03 9:04 ` [PATCH 1/5] net/tls: handle MSG_EOR for tls_sw TX flow Hannes Reinecke
2023-07-03 9:04 ` [PATCH 2/5] net/tls: handle MSG_EOR for tls_device " Hannes Reinecke
2023-07-03 9:04 ` [PATCH 3/5] selftests/net/tls: add test for MSG_EOR Hannes Reinecke
2023-07-03 9:04 ` [PATCH 4/5] net/tls: split tls_rx_reader_lock Hannes Reinecke
2023-07-03 10:06 ` Sagi Grimberg
2023-07-03 10:21 ` Hannes Reinecke
2023-07-05 20:55 ` Jakub Kicinski
2023-07-03 9:04 ` [PATCH 5/5] net/tls: implement ->read_sock() Hannes Reinecke
2023-07-04 7:56 ` Paolo Abeni
2023-07-03 10:08 ` [PATCHv6 0/5] net/tls: fixes for NVMe-over-TLS Sagi Grimberg
2023-07-03 10:20 ` Hannes Reinecke
2023-07-03 12:13 ` Hannes Reinecke
2023-07-03 12:19 ` Hannes Reinecke
2023-07-03 12:26 ` David Howells
2023-07-03 12:33 ` Sagi Grimberg
2023-07-03 13:15 ` Hannes Reinecke
2023-07-03 13:42 ` Sagi Grimberg
2023-07-03 13:46 ` Hannes Reinecke
2023-07-03 14:01 ` Sagi Grimberg
2023-07-03 13:57 ` Hannes Reinecke
2023-07-03 14:10 ` Sagi Grimberg
2023-07-03 12:35 ` Hannes Reinecke
2023-07-03 12:45 ` David Howells [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=874611.1688388330@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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).