linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Kriish Sharma <kriish.sharma2006@gmail.com>,
	skhan@linuxfoundation.org, maddy@linux.ibm.com,
	mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, christophe.leroy@csgroup.eu,
	npiggin@gmail.com, linux-kernel-mentees@lists.linux.dev,
	Kriish Sharma <kriish.sharma2006@gmail.com>
Subject: Re: [PATCH] docs/powerpc: add htm.rst to toctree to fix warning
Date: Wed, 30 Jul 2025 14:51:20 -0600	[thread overview]
Message-ID: <87qzxxtnav.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250730202752.8508-1-kriish.sharma2006@gmail.com>

Kriish Sharma <kriish.sharma2006@gmail.com> writes:

> The htm.rst file was not included in any toctree, leading to a Sphinx
> warning when building documentation.
>
> Include it in Documentation/arch/powerpc/index.rst to fix the warning.
>
> Signed-off-by: Kriish Sharma <kriish.sharma2006@gmail.com>
> ---
>  Documentation/arch/powerpc/index.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/arch/powerpc/index.rst b/Documentation/arch/powerpc/index.rst
> index 0560cbae5fa1..ae0280383315 100644
> --- a/Documentation/arch/powerpc/index.rst
> +++ b/Documentation/arch/powerpc/index.rst
> @@ -36,7 +36,7 @@ powerpc
>      vas-api
>      vcpudispatch_stats
>      vmemmap_dedup
> -
> +    htm
>      features

Thanks...but we already have two conflicting versions of this fix headed
upstream, so a third is probably not needed :)

jo


      reply	other threads:[~2025-07-30 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30 20:27 [PATCH] docs/powerpc: add htm.rst to toctree to fix warning Kriish Sharma
2025-07-30 20:51 ` Jonathan Corbet [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=87qzxxtnav.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=christophe.leroy@csgroup.eu \
    --cc=kriish.sharma2006@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=skhan@linuxfoundation.org \
    /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).