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>,
"Darrick J. Wong" <djwong@kernel.org>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH] Documentation: ext4: atomic_writes: Remove cross-reference labels
Date: Tue, 10 Jun 2025 16:11:59 +0700 [thread overview]
Message-ID: <20250610091200.54075-2-bagasdotme@gmail.com> (raw)
Sphinx reports htmldocs warnings on ext4 atomic block writes docs:
Documentation/filesystems/ext4/atomic_writes.rst:5: WARNING: duplicate label atomic_writes, other instance in Documentation/filesystems/ext4/atomic_writes.rst
Documentation/filesystems/ext4/atomic_writes.rst:207: WARNING: duplicate label atomic_write_bdev_support, other instance in Documentation/filesystems/ext4/atomic_writes.rst
These warnings reference duplicated cross-reference labels to themselves in
the same doc, which are because atomic_writes.rst is transcluded in
overview.rst via include:: directive, thus the culprit docs get processed
twice.
Remove the labels to fix the warnings.
Fixes: 0bf1f51e34c4 ("ext4: Add atomic block write documentation")
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/ext4/atomic_writes.rst | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/Documentation/filesystems/ext4/atomic_writes.rst b/Documentation/filesystems/ext4/atomic_writes.rst
index f65767df3620d5..f1a086aa026b1b 100644
--- a/Documentation/filesystems/ext4/atomic_writes.rst
+++ b/Documentation/filesystems/ext4/atomic_writes.rst
@@ -1,5 +1,4 @@
.. SPDX-License-Identifier: GPL-2.0
-.. _atomic_writes:
Atomic Block Writes
-------------------------
@@ -154,7 +153,7 @@ Creating Filesystems with Atomic Write Support
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
First check the atomic write units supported by block device.
-See :ref:`atomic_write_bdev_support` for more details.
+See "Hardware Support" section below for more details.
For single-fsblock atomic writes with a larger block size
(on systems with block size < page size):
@@ -201,7 +200,6 @@ details:
The STATX_ATTR_WRITE_ATOMIC flag in ``statx->attributes`` is set if atomic
writes are supported.
-.. _atomic_write_bdev_support:
Hardware Support
----------------
base-commit: d3f825032091fc14c7d5e34bcd54317ae4246903
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-06-10 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:11 Bagas Sanjaya [this message]
2025-06-11 16:48 ` [PATCH] Documentation: ext4: atomic_writes: Remove cross-reference labels Darrick J. Wong
2025-06-11 17:05 ` Jonathan Corbet
2025-06-12 0:07 ` Bagas Sanjaya
2025-06-12 1:09 ` Darrick J. Wong
2025-06-12 2:48 ` Bagas Sanjaya
2025-06-12 3:14 ` Bagas Sanjaya
2025-06-12 12:22 ` Jonathan Corbet
2025-06-12 12:20 ` 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=20250610091200.54075-2-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 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.