From: Jonathan Corbet <corbet@lwn•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Madhavan Srinivasan <maddy@linux•ibm.com>,
Michael Ellerman <mpe@ellerman•id.au>
Cc: PowerPC <linuxppc-dev@lists•ozlabs.org>,
Vishal Parmar <vishistriker@gmail•com>,
Brigham Campbell <me@brighamcampbell•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the jc_docs tree
Date: Wed, 30 Jul 2025 07:01:21 -0600 [thread overview]
Message-ID: <87cy9hx272.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250730102931.6334022c@canb.auug.org.au>
Stephen Rothwell <sfr@canb•auug.org.au> writes:
> Hi all,
>
> After merging the jc_docs tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/arch/powerpc/index.rst:7: WARNING: duplicated entry found in toctree: arch/powerpc/htm
>
> Introduced by commit
>
> c361f76da696 ("docs: powerpc: Add htm.rst to table of contents")
>
> interacting with commit
>
> 19122a7c28ed ("docs: powerpc: add htm.rst to toctree")
>
> from the powerpc tree.
Did that just get added there? I've had that fix since early June...I'd
rather not drop it (and have to redo my 6.17 pull request) now if
possible...
Thanks,
jon
next prev parent reply other threads:[~2025-07-30 13:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 0:29 linux-next: build warning after merge of the jc_docs tree Stephen Rothwell
2025-07-30 13:01 ` Jonathan Corbet [this message]
2025-07-30 14:30 ` Christophe Leroy
2025-07-30 15:14 ` Randy Dunlap
2025-07-30 14:31 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 7:28 Stephen Rothwell
2023-12-18 14:18 ` Jonathan Corbet
2023-12-19 23:59 ` Randy Dunlap
2023-12-20 0:02 ` Jonathan Corbet
2023-12-20 0:04 ` Randy Dunlap
2021-02-23 5:19 Stephen Rothwell
2021-01-13 4:14 Stephen Rothwell
2021-01-13 4:12 Stephen Rothwell
2021-01-13 4:18 ` Stephen Rothwell
2021-01-13 4:07 Stephen Rothwell
2021-01-13 23:27 ` Jonathan Corbet
2021-01-21 2:07 ` 司延腾
2021-01-21 18:30 ` Jonathan Corbet
2020-12-07 7:52 Stephen Rothwell
2020-11-16 6:03 Stephen Rothwell
2020-12-14 19:51 ` Stephen Rothwell
2020-12-14 20:17 ` 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=87cy9hx272.fsf@trenco.lwn.net \
--to=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=me@brighamcampbell$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=vishistriker@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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