From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux AFS <linux-afs@lists.infradead.org>,
Linux Filesystems Development <linux-fsdevel@vger.kernel.org>
Cc: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.com>,
Jonathan Corbet <corbet@lwn.net>,
Damien Le Moal <dlemoal@kernel.org>,
Naohiro Aota <naohiro.aota@wdc.com>,
Johannes Thumshirn <jth@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Daniel Palmer <daniel.palmer@sony.com>
Subject: [PATCH 3/5] Documentation: dax: Demote "Enabling DAX on xfs and ext4" subsections
Date: Wed, 26 Nov 2025 09:55:09 +0700 [thread overview]
Message-ID: <20251126025511.25188-4-bagasdotme@gmail.com> (raw)
In-Reply-To: <20251126025511.25188-1-bagasdotme@gmail.com>
Subsections of "Enabling DAX on xfs and ext4" section (both "Summary"
and "Details") are marked up as section heading instead, which makes
their way to filesystems toctree entry. Demote them.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/dax.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/dax.rst b/Documentation/filesystems/dax.rst
index e0631d5f6251d4..f9243d45ce1280 100644
--- a/Documentation/filesystems/dax.rst
+++ b/Documentation/filesystems/dax.rst
@@ -38,7 +38,7 @@ Enabling DAX on xfs and ext4
----------------------------
Summary
--------
+~~~~~~~
1. There exists an in-kernel file access mode flag `S_DAX` that corresponds to
the statx flag `STATX_ATTR_DAX`. See the manpage for statx(2) for details
@@ -95,7 +95,7 @@ Summary
Details
--------
+~~~~~~~
There are 2 per-file dax flags. One is a persistent inode setting (`FS_XFLAG_DAX`)
and the other is a volatile flag indicating the active state of the feature
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-11-26 2:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 2:55 [PATCH 0/5] Assorted filesystem docs formatting Bagas Sanjaya
2025-11-26 2:55 ` [PATCH 1/5] Documentation: afs: Use proper bullet for bullet lists Bagas Sanjaya
2025-11-27 0:43 ` Randy Dunlap
2025-11-26 2:55 ` [PATCH 2/5] Documentation: dax: Coalesce "See also" filesystem pointers into list Bagas Sanjaya
2025-11-27 0:43 ` Randy Dunlap
2025-11-26 2:55 ` Bagas Sanjaya [this message]
2025-11-27 0:43 ` [PATCH 3/5] Documentation: dax: Demote "Enabling DAX on xfs and ext4" subsections Randy Dunlap
2025-11-26 2:55 ` [PATCH 4/5] Documentation: zonefs: Separate mount options list Bagas Sanjaya
2025-11-26 4:17 ` Damien Le Moal
2025-11-27 0:43 ` Randy Dunlap
2025-11-26 2:55 ` [PATCH 5/5] Documentation: zonefs: Format error processing table Bagas Sanjaya
2025-11-26 4:17 ` Damien Le Moal
2025-11-27 0:44 ` Randy Dunlap
2025-11-26 9:28 ` [PATCH 1/5] Documentation: afs: Use proper bullet for bullet lists David Howells
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=20251126025511.25188-4-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=daniel.palmer@sony.com \
--cc=dhowells@redhat.com \
--cc=dlemoal@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=jth@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=naohiro.aota@wdc.com \
/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).