From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>
Cc: Shuai Xue <xueshuai@linux.alibaba.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the pci tree
Date: Mon, 5 Jan 2026 16:00:00 +1100 [thread overview]
Message-ID: <20260105160000.0368ec8d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
Hi all,
After merging the pci tree, today's linux-next build (htmldocs) produced
these warnings:
Documentation/trace/events-pci.rst:43: ERROR: Unexpected indentation. [docutils]
Documentation/trace/events-pci.rst:74: ERROR: Unexpected indentation. [docutils]
Documentation/trace/events-pci.rst: WARNING: document isn't included in any toctree [toc.not_included]
Introduced by commit
d0eb853678a2 ("Documentation: tracing: Add PCI tracepoint documentation")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-01-05 5:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 5:00 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 5:09 linux-next: build warnings after merge of the pci tree Stephen Rothwell
2024-02-06 20:21 ` Philipp Stanner
2022-03-01 2:59 Stephen Rothwell
2022-03-01 15:01 ` Bjorn Helgaas
2018-10-02 0:26 Stephen Rothwell
2018-10-02 13:47 ` Bjorn Helgaas
2016-06-20 1:52 Stephen Rothwell
2016-06-20 19:11 ` Bjorn Helgaas
2016-06-21 1:08 ` Stephen Rothwell
2016-06-21 1:27 ` Bjorn Helgaas
[not found] <EDA0A4495861324DA2618B4C45DCB3EE612CE1@blrx3m08.blr.amer.dell.com>
2010-08-02 12:44 ` Narendra K
2010-08-02 1:18 Stephen Rothwell
2010-08-02 1:38 ` Stephen Rothwell
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=20260105160000.0368ec8d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=xueshuai@linux.alibaba.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