From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Dai Ngo <Dai.Ngo@oracle.com>, Jeff Layton <jlayton@kernel.org>,
NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 1/4] NFSD/blocklayout: Fix minlength check in proc_layoutget
Date: Fri, 3 Oct 2025 21:22:17 -0700 [thread overview]
Message-ID: <aOCg-YF0v_soB2zS@infradead.org> (raw)
In-Reply-To: <3137a3d5-1377-49e3-a86e-e41c1afc9666@oracle.com>
On Fri, Oct 03, 2025 at 10:11:15AM -0400, Chuck Lever wrote:
> As author of the pNFS block layout code and the related specifications,
> and a frequent reviewer, would you be interested in being added as an
> official NFSD subsystem reviewer? If so, please post a patch that
> updates MAINTAINERS as you would like it to appear.
Will do.
next prev parent reply other threads:[~2025-10-04 4:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 20:31 [PATCH v2 0/4] NFSD: Impl multiple extents in block/scsi layoutget Sergey Bashirov
2025-10-02 20:31 ` [PATCH v2 1/4] NFSD/blocklayout: Fix minlength check in proc_layoutget Sergey Bashirov
2025-10-03 6:54 ` Christoph Hellwig
2025-10-03 14:11 ` Chuck Lever
2025-10-04 4:22 ` Christoph Hellwig [this message]
2025-10-02 20:31 ` [PATCH v2 2/4] NFSD/blocklayout: Extract extent mapping from proc_layoutget Sergey Bashirov
2025-10-03 6:56 ` Christoph Hellwig
2025-10-02 20:31 ` [PATCH v2 3/4] NFSD/blocklayout: Introduce layout content structure Sergey Bashirov
2025-10-03 6:57 ` Christoph Hellwig
2025-10-02 20:31 ` [PATCH v2 4/4] NFSD/blocklayout: Support multiple extents per LAYOUTGET Sergey Bashirov
2025-10-03 6:58 ` Christoph Hellwig
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=aOCg-YF0v_soB2zS@infradead.org \
--to=hch@infradead.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox