From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Saeed Mahameed <saeedm@nvidia.com>
Cc: Maher Sanalla <msanalla@nvidia.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 origin tree
Date: Mon, 8 May 2023 14:39:35 +1000 [thread overview]
Message-ID: <20230508143935.2cc24467@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
Hi all,
While building Linus' tree, today's linux-next build (htmldocs)
produced these warnings:
Documentation/networking/device_drivers/ethernet/mellanox/mlx5/devlink.rst:287: ERROR: Unexpected indentation.
Documentation/networking/device_drivers/ethernet/mellanox/mlx5/devlink.rst:288: WARNING: Block quote ends without a blank line; unexpected unindent.
Documentation/networking/device_drivers/ethernet/mellanox/mlx5/devlink.rst:290: ERROR: Unexpected indentation.
Introduced by commit
cf14af140a5a ("net/mlx5e: Add vnic devlink health reporter to representors")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-05-08 4:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 4:39 Stephen Rothwell [this message]
2023-05-08 6:31 ` linux-next: build warnings after merge of the origin tree Maher Sanalla
-- strict thread matches above, loose matches on Subject: below --
2022-06-20 8:02 Stephen Rothwell
2021-02-18 21:02 Stephen Rothwell
2021-02-19 15:33 ` Vitaly Kuznetsov
2021-02-19 16:01 ` Paolo Bonzini
2021-02-23 21:56 ` Stephen Rothwell
2021-02-26 1:57 ` 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=20230508143935.2cc24467@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=msanalla@nvidia.com \
--cc=saeedm@nvidia.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;
as well as URLs for NNTP newsgroup(s).