From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Christian Brauner <brauner@kernel.org>
Cc: Seth Forshee <sforshee@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fat: port to vfs{g,u}id_t and associated helpers
Date: Fri, 09 Sep 2022 21:33:12 +0900 [thread overview]
Message-ID: <878rmsralz.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20220909102656.pqlipjit2zlp4vdx@wittgenstein> (Christian Brauner's message of "Fri, 9 Sep 2022 12:26:56 +0200")
Christian Brauner <brauner@kernel.org> writes:
> On Fri, Sep 09, 2022 at 07:01:07PM +0900, OGAWA Hirofumi wrote:
>> Christian Brauner <brauner@kernel.org> writes:
>>
>> > A while ago we introduced a dedicated vfs{g,u}id_t type in commit
>> > 1e5267cd0895 ("mnt_idmapping: add vfs{g,u}id_t"). We already switched
>> > over a good part of the VFS. Ultimately we will remove all legacy
>> > idmapped mount helpers that operate only on k{g,u}id_t in favor of the
>> > new type safe helpers that operate on vfs{g,u}id_t.
>>
>> If consistent with other parts in kernel, looks good.
>>
>> Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
>
> Just to make sure: will you be taking this patch yourself or should I?
Ah, I was expecting almost all convert patches goes at once via you or
vfs git. However, if you want this goes via me, please let me know.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2022-09-09 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:30 [PATCH] fat: port to vfs{g,u}id_t and associated helpers Christian Brauner
2022-09-09 10:01 ` OGAWA Hirofumi
2022-09-09 10:26 ` Christian Brauner
2022-09-09 12:33 ` OGAWA Hirofumi [this message]
2022-09-19 8:07 ` Christian Brauner
2022-09-19 11:24 ` OGAWA Hirofumi
2022-09-19 14:53 ` Christian Brauner
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=878rmsralz.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@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