From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: kernel-tls-handshake@lists.linux.dev, netdev@vger.kernel.org,
dan.carpenter@linaro.org
Subject: Re: [PATCH 0/5] Bug fixes for net/handshake
Date: Fri, 5 May 2023 16:47:15 -0700 [thread overview]
Message-ID: <20230505164715.55a12c77@kernel.org> (raw)
In-Reply-To: <ZFWOWErJ6eR/RX/X@manet.1015granger.net>
On Fri, 5 May 2023 19:16:40 -0400 Chuck Lever wrote:
> On Fri, May 05, 2023 at 01:39:18PM -0700, Jakub Kicinski wrote:
> > On Thu, 04 May 2023 11:24:12 -0400 Chuck Lever wrote:
> > > I plan to send these as part of a 6.4-rc PR.
> >
> > Can you elaborate? You'll send us the same code as PR?
> > I'm about to send the first batch of fixes to Linus,
> > I was going to apply this series.
>
> Since I am listed as a maintainer/supporter of net/handshake, I
> assumed I can and should be sending changes through nfsd or some
> other repo I can commit to.
>
> netdev@ is also listed in MAINTAINERS, so I Cc'd you all on this
> series. I did not intend for you to be responsible for merging the
> series. We'll need to agree on a workflow going forward.
Let me talk to DaveM and Paolo -- with NFS being the main user
taking it via your trees is likely fine. But if it's a generic TLS
handshake and other users will appear - netdev trees may be a more
natural central point :S DaveM and Paolo are more familiar with
existing cases of similar nature (rxrpc?)..
> Since you had some review questions about one of the patches,
> maybe that patch should not be merged at this time by either of us.
Right, I noticed the cover message first then started looking more
in depth at the code :)
next prev parent reply other threads:[~2023-05-05 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:24 [PATCH 0/5] Bug fixes for net/handshake Chuck Lever
2023-05-04 15:24 ` [PATCH 1/5] net/handshake: Remove unneeded check from handshake_dup() Chuck Lever
2023-05-05 13:15 ` Simon Horman
2023-05-04 15:25 ` [PATCH 2/5] net/handshake: Fix handshake_dup() ref counting Chuck Lever
2023-05-05 13:15 ` Simon Horman
2023-05-05 20:58 ` Jakub Kicinski
2023-05-05 23:28 ` Chuck Lever
2023-05-04 15:25 ` [PATCH 3/5] net/handshake: Fix uninitialized local variable Chuck Lever
2023-05-05 13:15 ` Simon Horman
2023-05-04 15:25 ` [PATCH 4/5] net/handshake: handshake_genl_notify() shouldn't ignore @flags Chuck Lever
2023-05-05 13:15 ` Simon Horman
2023-05-04 15:26 ` [PATCH 5/5] net/handshake: Enable the SNI extension to work properly Chuck Lever
2023-05-05 13:16 ` Simon Horman
2023-05-05 20:39 ` [PATCH 0/5] Bug fixes for net/handshake Jakub Kicinski
2023-05-05 23:16 ` Chuck Lever
2023-05-05 23:47 ` Jakub Kicinski [this message]
2023-05-05 23:58 ` Chuck Lever
2023-05-08 5:51 ` Paolo Abeni
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=20230505164715.55a12c77@kernel.org \
--to=kuba@kernel.org \
--cc=cel@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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.