From: Christian Brauner <brauner@kernel.org>
To: Alexander Mikhalitsyn <alexander@mihalicyn.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Seth Forshee <sforshee@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: filesystems: idmappings: clarify from where idmappings are taken
Date: Thu, 10 Aug 2023 15:40:45 +0200 [thread overview]
Message-ID: <20230810-leiht-aufnimmt-21ab1cced78d@brauner> (raw)
In-Reply-To: <20230625182047.26854-1-aleksandr.mikhalitsyn@canonical.com>
On Sun, 25 Jun 2023 20:20:47 +0200, Alexander Mikhalitsyn wrote:
> Let's clarify from where we take idmapping of each type:
> - caller
> - filesystem
> - mount
>
>
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc 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.misc
[1/1] docs: filesystems: idmappings: clarify from where idmappings are taken
https://git.kernel.org/vfs/vfs/c/b4704cb65f47
prev parent reply other threads:[~2023-08-10 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 18:20 [PATCH v2] docs: filesystems: idmappings: clarify from where idmappings are taken Alexander Mikhalitsyn
2023-08-10 13:40 ` 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=20230810-leiht-aufnimmt-21ab1cced78d@brauner \
--to=brauner@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sforshee@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).