From: Christoph Hellwig <hch@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] fs: start to split up fs.h
Date: Wed, 5 Nov 2025 04:55:34 -0800 [thread overview]
Message-ID: <aQtJRisTtkX-Jzen@infradead.org> (raw)
In-Reply-To: <20251104-work-fs-header-v1-0-fb39a2efe39e@kernel.org>
On Tue, Nov 04, 2025 at 03:46:31PM +0100, Christian Brauner wrote:
> Take first steps to split up fs.h. Add fs_super_types.h and fs_super.h
> headers that contain the types and functions associated with super
> blocks respectively.
We have this nice concept called directories for namespace prefixes.
Why not include/linux/fs/*.h for all these split out bits?
next prev parent reply other threads:[~2025-11-05 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 14:46 [PATCH 0/3] fs: start to split up fs.h Christian Brauner
2025-11-04 14:46 ` [PATCH 1/3] fs: rename fs_types.h to fs_dirent.h Christian Brauner
2025-11-04 14:46 ` [PATCH 2/3] fs: add fs_super_types header Christian Brauner
2025-11-04 14:46 ` [PATCH 3/3] fs: add fs_super.h header Christian Brauner
2025-11-05 12:55 ` Christoph Hellwig [this message]
2025-11-05 13:13 ` [PATCH 0/3] fs: start to split up fs.h Christian Brauner
2025-11-05 13:48 ` 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=aQtJRisTtkX-Jzen@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).