From: Jakub Kicinski <kuba@kernel.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH 4/5] net/tls: split tls_rx_reader_lock
Date: Wed, 5 Jul 2023 13:55:48 -0700 [thread overview]
Message-ID: <20230705135548.52db9949@kernel.org> (raw)
In-Reply-To: <0e230fdf-6af6-926f-305e-2f34ac6a6812@suse.de>
On Mon, 3 Jul 2023 12:21:32 +0200 Hannes Reinecke wrote:
> > Nit: I still think tls_rx_reader_enter/tls_rx_reader_exit are more
> > appropriate names.
>
> I don't mind either way, but I've interpreted the comments from Jakub
> that he'd like this naming better.
>
> Jakub?
Slight preference for enter/leave (leave rather than exit).
next prev parent reply other threads:[~2023-07-05 20:55 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 [this message]
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
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=20230705135548.52db9949@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@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 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.