From: Simon Horman <horms@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Jakub Kicinski <kuba@kernel.org>, Neil Brown <neilb@suse.de>,
Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
netdev <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Lex Siegel <usiegl00@gmail.com>
Subject: Re: [PATCH net v2] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
Date: Tue, 2 Jul 2024 13:46:36 +0100 [thread overview]
Message-ID: <20240702124636.GI598357@kernel.org> (raw)
In-Reply-To: <39757894-2C57-4DD6-AF93-25EA35C87C3D@oracle.com>
On Mon, Jul 01, 2024 at 02:04:22PM +0000, Chuck Lever III wrote:
> > On Jul 1, 2024, at 6:57 AM, Simon Horman <horms@kernel.org> wrote:
> > On Fri, Jun 28, 2024 at 01:19:49PM -0400, Chuck Lever wrote:
> >> On Fri, Jun 28, 2024 at 06:31:23PM +0200, Daniel Borkmann wrote:
...
> >> Hi Daniel -
> >>
> >> I know this is not documented in MAINTAINERS, but changes to
> >> net/sunrpc/xprtsock.c go to Anna Schumaker and Trond Myklebust,
> >> cc: linux-nfs@vger.
> >
> > Would it be possible to update MAINTAINERS accordingly?
>
> I can do it, of course, but I'd like to discuss this
> with the NFS client maintainers to ensure they agree
> on how the files are divided between the trees.
Hi Chuck,
Thanks in advance for raising this with the NFS client maintainers.
I do think it would be nice to resolve.
next prev parent reply other threads:[~2024-07-02 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 16:31 [PATCH net v2] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket Daniel Borkmann
2024-07-03 7:01 ` [PATCH net v3] " Daniel Borkmann
2024-06-28 20:35 ` Daniel Borkmann
2024-06-28 17:19 ` [PATCH net v2] " Chuck Lever
2024-07-01 10:57 ` Simon Horman
2024-07-01 14:04 ` Chuck Lever III
2024-07-02 12:46 ` Simon Horman [this message]
2024-07-02 12:56 ` Fwd: " Chuck Lever III
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=20240702124636.GI598357@kernel.org \
--to=horms@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=daniel@iogearbox.net \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=kuba@kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=tom@talpey.com \
--cc=usiegl00@gmail.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.