From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: create an entry for exportfs
Date: Fri, 27 Oct 2023 15:10:37 +0200 [thread overview]
Message-ID: <20231027-infoabend-glanz-7617798f5fc5@brauner> (raw)
In-Reply-To: <20231026205553.143556-1-amir73il@gmail.com>
On Thu, 26 Oct 2023 23:55:53 +0300, Amir Goldstein wrote:
> Split the exportfs entry from the nfsd entry and add myself as reviewer.
>
>
Looks useful to clarify this. I've create vfs-6.7.* tags yesterday I
plan on sending this one either at the end of next week or in week 2
together with other possible fixes.
---
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] MAINTAINERS: create an entry for exportfs
https://git.kernel.org/vfs/vfs/c/7723a9a55be9
prev parent reply other threads:[~2023-10-27 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 20:55 [PATCH] MAINTAINERS: create an entry for exportfs Amir Goldstein
2023-10-27 6:08 ` Christoph Hellwig
2023-10-27 6:35 ` Amir Goldstein
2023-10-27 7:30 ` Christoph Hellwig
2023-10-27 12:55 ` Amir Goldstein
2023-10-27 13:10 ` Christian Brauner [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=20231027-infoabend-glanz-7617798f5fc5@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).