From: Gao Xiang <xiang@kernel.org>
To: brauner@kernel.org
Cc: Giuseppe Scrivano <giuseppe@scrivano.org>,
linux-erofs@lists.ozlabs.org, xiang@kernel.org,
linux-fsdevel@vger.kernel.org, amir73il@gmail.com,
viro@zeniv.linux.org.uk, jack@suse.cz, hch@infradead.org
Subject: Re: [PATCH v7 1/2] fs: rename vfs_get_super() to get_tree_super() and export it
Date: Tue, 6 Oct 2026 13:08:50 +0200 [thread overview]
Message-ID: <asTWwqqx8RQfD9r7@MacBookPro> (raw)
In-Reply-To: <20261002163225.1258203-2-giuseppe@scrivano.org>
Hi Christian,
On Fri, Oct 02, 2026 at 06:31:43PM +0200, Giuseppe Scrivano wrote:
> Rename and export it so filesystems that need a custom superblock
> matching policy can reuse it directly instead of open-coding sget_fc()
> + fill_super(). No functional change.
>
> This is a preparatory fix for the next patch.
>
> Signed-off-by: Giuseppe Scrivano <giuseppe@scrivano.org>
Could you replace the previous patch in
https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/log/?h=vfs-7.4.shared.super
with this version?
It addresses Christoph's previous review, I could pick up the
updated branch then:
https://lore.kernel.org/r/arY9FCatWwCw418K@infradead.org
Thanks for Christoph and Jan's review here again!
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-10-06 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 16:31 [PATCH v7 0/2] erofs: share the superblock for file-backed mounts Giuseppe Scrivano
2026-10-02 16:31 ` [PATCH v7 1/2] fs: rename vfs_get_super() to get_tree_super() and export it Giuseppe Scrivano
2026-10-05 8:14 ` Christoph Hellwig
2026-10-05 12:38 ` Jan Kara
2026-10-06 11:08 ` Gao Xiang [this message]
2026-10-02 16:31 ` [PATCH v7 2/2] erofs: reuse superblock for file-backed mounts Giuseppe Scrivano
2026-10-12 16:23 ` Gao Xiang
2026-10-12 10:48 ` (subset) [PATCH v7 0/2] erofs: share the " 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=asTWwqqx8RQfD9r7@MacBookPro \
--to=xiang@kernel.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=giuseppe@scrivano.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.