From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jon Mason <jdmason@kudzu.us>,
NTB Mailing List <linux-ntb@googlegroups.com>
Cc: Frank Li <Frank.Li@nxp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the ntb tree
Date: Tue, 21 Jun 2022 20:02:35 +1000 [thread overview]
Message-ID: <20220621200235.211b2e32@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
Hi all,
After merging the ntb tree, today's linux-next build (htmldocs) produced
this warning:
Documentation/PCI/endpoint/pci-vntb-function.rst:82: WARNING: Unexpected indentation.
Documentation/PCI/endpoint/pci-vntb-howto.rst:131: WARNING: Title underline too short.
lspci Output at Host side
------------------------
Introduced by commit
0c4b285d9636 ("Documentation: PCI: Add specification for the PCI vNTB function device")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-06-21 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 10:02 Stephen Rothwell [this message]
[not found] ` <20220622095345.27121-1-bagasdotme@gmail.com>
2022-06-22 9:53 ` [PATCH 1/2] Documentation: PCI: Use code-block block for scratchpad registers diagram Bagas Sanjaya
2022-06-23 15:37 ` [EXT] " Frank Li
2022-06-22 9:53 ` [PATCH 2/2] Documentation: PCI: extend subheading underline for "lspci output" section Bagas Sanjaya
-- strict thread matches above, loose matches on Subject: below --
2019-07-16 3:03 linux-next: build warning after merge of the ntb tree Stephen Rothwell
2019-07-16 3:46 ` Logan Gunthorpe
2019-07-16 4:54 ` Stephen Rothwell
2019-07-16 6:02 ` Masahiro Yamada
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=20220621200235.211b2e32@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Frank.Li@nxp.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-ntb@googlegroups.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