From: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.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 pci tree
Date: Wed, 21 May 2025 21:10:29 +0900 [thread overview]
Message-ID: <20250521121029.GA143406@rocinante> (raw)
In-Reply-To: <20250521202640.53a4fc3d@canb.auug.org.au>
Hello,
> After merging the pci tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/PCI/rcar-pcie-firmware.rst: WARNING: document isn't included in any toctree
>
> Introduced by commit
>
> 2bdf6ffe9f66 ("PCI: rcar-gen4: Document how to obtain platform firmware")
Sorry about that! This should be fixed on the branch already, per:
https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?h=controller/rcar-gen4&id=003d15b30f3690b14315822439edc2c3f823c6cd
Hopefully, running the "make htmldocs" should not report warnings for this
new file any longer.
I will coordinate with Bjorn about pushing next, as he is working on
something that he might want to include there.
Thank you!
Krzysztof
next prev parent reply other threads:[~2025-05-21 12:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 10:26 linux-next: build warning after merge of the pci tree Stephen Rothwell
2025-05-21 12:10 ` Krzysztof Wilczyński [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-18 12:41 Stephen Rothwell
2025-03-03 7:26 Stephen Rothwell
2025-03-03 7:50 ` Krzysztof Wilczyński
2025-03-03 9:46 ` Krzysztof Wilczyński
2024-07-01 9:24 Stephen Rothwell
2024-07-01 19:37 ` Bjorn Helgaas
2024-07-01 20:15 ` Krzysztof Wilczyński
2024-07-02 6:59 ` Philipp Stanner
2020-09-09 2:38 Stephen Rothwell
2020-09-15 3:43 ` Stephen Rothwell
2020-09-09 2:37 Stephen Rothwell
2020-09-09 16:06 ` Rob Herring
2020-09-15 3:47 ` Stephen Rothwell
2020-09-15 10:53 ` Lorenzo Pieralisi
2020-09-15 17:22 ` Bjorn Helgaas
2020-09-02 1:07 Stephen Rothwell
2020-09-02 12:33 ` Bjorn Helgaas
2020-09-02 14:13 ` Vaibhav Gupta
2020-08-05 1:32 Stephen Rothwell
2020-08-05 2:29 ` Bjorn Helgaas
2016-06-23 1:51 Stephen Rothwell
2016-06-23 16:48 ` Bjorn Helgaas
2016-06-24 8:07 ` Johannes Thumshirn
2013-09-03 23:55 Stephen Rothwell
2013-09-03 23:59 ` Bjorn Helgaas
2012-12-10 9:03 Stephen Rothwell
2012-12-10 21:25 ` Bjorn Helgaas
2012-12-10 23:21 ` Bjorn Helgaas
2012-05-01 6:08 Stephen Rothwell
2012-05-01 7:35 ` Yinghai Lu
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=20250521121029.GA143406@rocinante \
--to=kwilczynski@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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