From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Filesystems Development <linux-fsdevel@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Miklos Szeredi <miklos@szeredi.hu>,
Luis Henriques <luis@igalia.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Bernd Schubert <bschubert@ddn.com>,
Amir Goldstein <amir73il@gmail.com>,
Chen Linxuan <chenlinxuan@uniontech.com>,
Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
James Morse <james.morse@arm.com>
Subject: [PATCH] Documentation: fuse: Consolidate FUSE docs into its own subdirectory
Date: Thu, 12 Jun 2025 10:22:39 +0700 [thread overview]
Message-ID: <20250612032239.17561-1-bagasdotme@gmail.com> (raw)
All four FUSE docs are currently in upper-level
Documentation/filesystems/ directory, but these are distinct as a group
of its own. Move them into Documentation/filesystems/fuse/ subdirectory.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
.../filesystems/{ => fuse}/fuse-io-uring.rst | 0
Documentation/filesystems/{ => fuse}/fuse-io.rst | 2 +-
.../filesystems/{ => fuse}/fuse-passthrough.rst | 0
Documentation/filesystems/{ => fuse}/fuse.rst | 6 +++---
Documentation/filesystems/fuse/index.rst | 14 ++++++++++++++
Documentation/filesystems/index.rst | 5 +----
MAINTAINERS | 2 +-
7 files changed, 20 insertions(+), 9 deletions(-)
rename Documentation/filesystems/{ => fuse}/fuse-io-uring.rst (100%)
rename Documentation/filesystems/{ => fuse}/fuse-io.rst (99%)
rename Documentation/filesystems/{ => fuse}/fuse-passthrough.rst (100%)
rename Documentation/filesystems/{ => fuse}/fuse.rst (99%)
create mode 100644 Documentation/filesystems/fuse/index.rst
diff --git a/Documentation/filesystems/fuse-io-uring.rst b/Documentation/filesystems/fuse/fuse-io-uring.rst
similarity index 100%
rename from Documentation/filesystems/fuse-io-uring.rst
rename to Documentation/filesystems/fuse/fuse-io-uring.rst
diff --git a/Documentation/filesystems/fuse-io.rst b/Documentation/filesystems/fuse/fuse-io.rst
similarity index 99%
rename from Documentation/filesystems/fuse-io.rst
rename to Documentation/filesystems/fuse/fuse-io.rst
index 6464de4266ad50..d736ac4cb48370 100644
--- a/Documentation/filesystems/fuse-io.rst
+++ b/Documentation/filesystems/fuse/fuse-io.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: GPL-2.0
==============
-Fuse I/O Modes
+FUSE I/O Modes
==============
Fuse supports the following I/O modes:
diff --git a/Documentation/filesystems/fuse-passthrough.rst b/Documentation/filesystems/fuse/fuse-passthrough.rst
similarity index 100%
rename from Documentation/filesystems/fuse-passthrough.rst
rename to Documentation/filesystems/fuse/fuse-passthrough.rst
diff --git a/Documentation/filesystems/fuse.rst b/Documentation/filesystems/fuse/fuse.rst
similarity index 99%
rename from Documentation/filesystems/fuse.rst
rename to Documentation/filesystems/fuse/fuse.rst
index 1e31e87aee68c5..5976828586f8df 100644
--- a/Documentation/filesystems/fuse.rst
+++ b/Documentation/filesystems/fuse/fuse.rst
@@ -1,8 +1,8 @@
.. SPDX-License-Identifier: GPL-2.0
-====
-FUSE
-====
+=============
+FUSE Overview
+=============
Definitions
===========
diff --git a/Documentation/filesystems/fuse/index.rst b/Documentation/filesystems/fuse/index.rst
new file mode 100644
index 00000000000000..393a845214da95
--- /dev/null
+++ b/Documentation/filesystems/fuse/index.rst
@@ -0,0 +1,14 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+======================================================
+FUSE (Filesystem in Userspace) Technical Documentation
+======================================================
+
+.. toctree::
+ :maxdepth: 2
+ :numbered:
+
+ fuse
+ fuse-io
+ fuse-io-uring
+ fuse-passthrough
diff --git a/Documentation/filesystems/index.rst b/Documentation/filesystems/index.rst
index 11a599387266a4..84c5a0d11b6df7 100644
--- a/Documentation/filesystems/index.rst
+++ b/Documentation/filesystems/index.rst
@@ -96,10 +96,7 @@ Documentation for filesystem implementations.
hfs
hfsplus
hpfs
- fuse
- fuse-io
- fuse-io-uring
- fuse-passthrough
+ fuse/index
inotify
isofs
nilfs2
diff --git a/MAINTAINERS b/MAINTAINERS
index a92290fffa163f..026afb50000346 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9898,7 +9898,7 @@ L: linux-fsdevel@vger.kernel.org
S: Maintained
W: https://github.com/libfuse/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git
-F: Documentation/filesystems/fuse*
+F: Documentation/filesystems/fuse/*
F: fs/fuse/
F: include/uapi/linux/fuse.h
base-commit: d3f825032091fc14c7d5e34bcd54317ae4246903
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-06-12 3:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 3:22 Bagas Sanjaya [this message]
2025-06-12 9:07 ` [PATCH] Documentation: fuse: Consolidate FUSE docs into its own subdirectory Miklos Szeredi
2025-06-12 9:09 ` Bernd Schubert
2025-06-12 10:53 ` Jeff Layton
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=20250612032239.17561-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=bschubert@ddn.com \
--cc=chenlinxuan@uniontech.com \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=james.morse@arm.com \
--cc=jlayton@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@igalia.com \
--cc=miklos@szeredi.hu \
/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).