From: Andre Luiz da Nobrega <andreluizrodriguescastro@gmail.com>
To: tytso@mit.edu
Cc: adilger.kernel@dilger.ca, corbet@lwn.net,
linux-ext4@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org
Subject: [PATCH] Fixed commit: Fixes Sphinx warnings about duplicate reference labels in Documentation/filesystems/ext4/atomic_writes.rst.
Date: Mon, 28 Jul 2025 22:32:00 -0300 [thread overview]
Message-ID: <20250729013200.84919-1-andreluizrodriguescastro@gmail.com> (raw)
Specifically, the label '.. _atomic_write_bdev_support:' was renamed to
'.. _atomic_write_bdev_support_section:' to ensure label uniqueness
within the document.
Signed-off-by: Andre Luiz da Nobrega <andreluizrodriguescastro@gmail.com>
---
Documentation/filesystems/ext4/atomic_writes.rst | 2 +-
warn_output.txt | 12 ++++++++++++
2 files changed, 13 insertions(+), 1 deletion(-)
create mode 100644 warn_output.txt
diff --git a/Documentation/filesystems/ext4/atomic_writes.rst b/Documentation/filesystems/ext4/atomic_writes.rst
index 80f83112d24d..e8cf983049b4 100644
--- a/Documentation/filesystems/ext4/atomic_writes.rst
+++ b/Documentation/filesystems/ext4/atomic_writes.rst
@@ -204,7 +204,7 @@ writes are supported.
.. _atomic_write_bdev_support_section:
Hardware Support
-----------------
+-----------------
The underlying storage device must support atomic write operations.
Modern NVMe and SCSI devices often provide this capability.
diff --git a/warn_output.txt b/warn_output.txt
new file mode 100644
index 000000000000..593c6fa5b65d
--- /dev/null
+++ b/warn_output.txt
@@ -0,0 +1,12 @@
+Using alabaster theme
+^[[91m/home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/filesystems/ext4/atomic_writes.rst:5: WARNING: duplicate label atomic_writes, other instance in /home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/filesystems/ext4/atomic_writes.rst^[[39;49;00m
+^[[91m/home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/filesystems/ext4/atomic_writes.rst:207: WARNING: duplicate label atomic_write_bdev_support, other instance in /home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/filesystems/ext4/atomic_writes.rst^[[39;49;00m
+^[[91mWARNING: ./drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:1068 struct member 'mcm' not described in 'mpc_funcs'^[[39;49;00m
+^[[91mWARNING: ./drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:1068 struct member 'rmcm' not described in 'mpc_funcs'^[[39;49;00m
+^[[91m/home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/gpu/drm-kms:360: ./drivers/gpu/drm/drm_fourcc.c:362: WARNING: Duplicate C declaration, also defined at gpu/drm-kms:35.
+Declaration is '.. c:function:: const struct drm_format_info * drm_format_info (u32 format)'.^[[39;49;00m
+^[[91m/home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/gpu/drm-kms:476: ./drivers/gpu/drm/drm_modeset_lock.c:375: WARNING: Duplicate C declaration, also defined at gpu/drm-kms:49.
+Declaration is '.. c:function:: int drm_modeset_lock (struct drm_modeset_lock *lock, struct drm_modeset_acquire_ctx *ctx)'.^[[39;49;00m
+^[[91m/home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/gpu/drm-uapi:557: ./drivers/gpu/drm/drm_ioctl.c:915: WARNING: Duplicate C declaration, also defined at gpu/drm-uapi:70.
+Declaration is '.. c:function:: bool drm_ioctl_flags (unsigned int nr, unsigned int *flags)'.^[[39;49;00m
+^[[91m/home/alkaleus/Documentos/PESSOAL/LFX_dev/linus_tree/Documentation/arch/powerpc/htm.rst: WARNING: document isn't included in any toctree^[[39;49;00m
--
2.50.1
next reply other threads:[~2025-07-29 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 1:32 Andre Luiz da Nobrega [this message]
2025-07-29 1:40 ` Randy Dunlap
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=20250729013200.84919-1-andreluizrodriguescastro@gmail.com \
--to=andreluizrodriguescastro@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®