From: bfields@fieldses.org (J. Bruce Fields)
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSD merge candidate for v5.11
Date: Mon, 30 Nov 2020 14:47:56 -0500 [thread overview]
Message-ID: <20201130194756.GB17322@fieldses.org> (raw)
In-Reply-To: <20201125145617.GA77389@pick.fieldses.org>
On Wed, Nov 25, 2020 at 09:56:17AM -0500, J. Bruce Fields wrote:
> On Tue, Nov 24, 2020 at 07:36:21PM -0500, Chuck Lever wrote:
> > Declarations for most other generic_* functions are in fs.h.
> > But OK, moved, and the series pushed.
> >
> > So I think the btrfs/ext4/xfs-specific changes might need
> > sign-off by those maintainers.
>
> And nfs, I think that's the one I'm mostly likely to have messed up,
> actually....
>
> > Should I post this series to linux-fsdevel? Or, Bruce, do you want to?
>
> I think I should do it.
I resent, and just left out the patches that touch btrfs, ext4, xfs, and
nfs. Those can go in later.
--b.
prev parent reply other threads:[~2020-11-30 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 22:51 NFSD merge candidate for v5.11 Chuck Lever
2020-11-24 23:14 ` Jeff Layton
2020-11-25 0:36 ` Chuck Lever
2020-11-25 14:56 ` J. Bruce Fields
2020-11-30 19:47 ` J. Bruce Fields [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=20201130194756.GB17322@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox