linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Andre Luiz da Nobrega <andreluizrodriguescastro@gmail.com>,
	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
Subject: Re: [PATCH] docs: ext4: fix duplicate Sphinx labels in atomic_writes.rst
Date: Mon, 28 Jul 2025 18:03:58 -0700	[thread overview]
Message-ID: <0b5d7ca5-cc85-4f6b-b417-0d237d9d45a4@infradead.org> (raw)
In-Reply-To: <20250729005628.68795-1-andreluizrodriguescastro@gmail.com>

Hi,

It seems that the patch and the $Subject do not agree.


On 7/28/25 5:56 PM, Andre Luiz da Nobrega wrote:
> Fixes Sphinx warnings about duplicate reference labels in
> Documentation/filesystems/ext4/atomic_writes.rst.
> 
> 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/arch/powerpc/index.rst | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/arch/powerpc/index.rst b/Documentation/arch/powerpc/index.rst
> index 0560cbae5fa1..ce39b54b5a7d 100644
> --- a/Documentation/arch/powerpc/index.rst
> +++ b/Documentation/arch/powerpc/index.rst
> @@ -6,7 +6,7 @@ powerpc
>  
>  .. toctree::
>      :maxdepth: 1
> -
> +    
>      associativity
>      booting
>      bootwrapper
> @@ -20,6 +20,7 @@ powerpc
>      elfnote
>      firmware-assisted-dump
>      hvcs
> +    htm 
>      imc
>      isa-versions
>      kaslr-booke32

-- 
~Randy


      reply	other threads:[~2025-07-29  1:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29  0:56 [PATCH] docs: ext4: fix duplicate Sphinx labels in atomic_writes.rst Andre Luiz da Nobrega
2025-07-29  1:03 ` Randy Dunlap [this message]

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=0b5d7ca5-cc85-4f6b-b417-0d237d9d45a4@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=andreluizrodriguescastro@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).