From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux ext4 <linux-ext4@vger.kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jonathan Corbet <corbet@lwn.net>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 5/5] Documentation: ext4: Move inode table short docs into its own file
Date: Fri, 20 Jun 2025 17:56:44 +0700 [thread overview]
Message-ID: <20250620105643.25141-7-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250620105643.25141-2-bagasdotme@gmail.com>
The short description of inode table is in bitmaps.rst alongside the
proper bitmpas documentation. The docs file is short enough that it fits
whole browser screen on desktop, which implies that when readers click
"Inode Table", they will essentially see bitmaps docs.
Move inode table short description.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/ext4/bitmaps.rst | 7 -------
Documentation/filesystems/ext4/globals.rst | 1 +
Documentation/filesystems/ext4/inode_table.rst | 9 +++++++++
3 files changed, 10 insertions(+), 7 deletions(-)
create mode 100644 Documentation/filesystems/ext4/inode_table.rst
diff --git a/Documentation/filesystems/ext4/bitmaps.rst b/Documentation/filesystems/ext4/bitmaps.rst
index 91c45d86e9bb56..9d7d7b083a258c 100644
--- a/Documentation/filesystems/ext4/bitmaps.rst
+++ b/Documentation/filesystems/ext4/bitmaps.rst
@@ -19,10 +19,3 @@ necessarily the case that no blocks are in use -- if ``meta_bg`` is set,
the bitmaps and group descriptor live inside the group. Unfortunately,
ext2fs_test_block_bitmap2() will return '0' for those locations,
which produces confusing debugfs output.
-
-Inode Table
------------
-Inode tables are statically allocated at mkfs time. Each block group
-descriptor points to the start of the table, and the superblock records
-the number of inodes per group. See the section on inodes for more
-information.
diff --git a/Documentation/filesystems/ext4/globals.rst b/Documentation/filesystems/ext4/globals.rst
index 2264b76e873cc9..c6a6abce818a17 100644
--- a/Documentation/filesystems/ext4/globals.rst
+++ b/Documentation/filesystems/ext4/globals.rst
@@ -11,6 +11,7 @@ have static metadata at fixed locations.
super
group_descr
bitmaps
+ inode_table
mmp
journal
orphan
diff --git a/Documentation/filesystems/ext4/inode_table.rst b/Documentation/filesystems/ext4/inode_table.rst
new file mode 100644
index 00000000000000..f7900a52c0d5da
--- /dev/null
+++ b/Documentation/filesystems/ext4/inode_table.rst
@@ -0,0 +1,9 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+Inode Table
+-----------
+
+Inode tables are statically allocated at mkfs time. Each block group
+descriptor points to the start of the table, and the superblock records
+the number of inodes per group. See :doc:`inode documentation <inodes>`
+for more information on inode table layout.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-06-20 10:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:56 [PATCH 0/5] ext4 docs toctree reorganization Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 1/5] Documentation: ext4: Convert includes into toctrees Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 2/5] Documentation: ext4: Reduce toctree depth Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 3/5] Documentation: ext4: atomic_writes: Demote last three sections Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 4/5] Documentation: ext4: blockgroup: Add explicit title heading Bagas Sanjaya
2025-06-20 10:56 ` Bagas Sanjaya [this message]
2025-06-30 0:53 ` [PATCH 0/5] ext4 docs toctree reorganization Bagas Sanjaya
2025-06-30 15:22 ` Darrick J. Wong
2025-07-01 19:11 ` Jonathan Corbet
2025-07-01 19:45 ` Darrick J. Wong
2025-07-01 19:52 ` Jonathan Corbet
2025-07-01 21:24 ` Theodore Ts'o
2025-07-02 22:59 ` Jonathan Corbet
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=20250620105643.25141-7-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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).