From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the hwmon-staging tree
Date: Tue, 7 Jun 2022 16:35:11 +0700 [thread overview]
Message-ID: <Yp8bz4Yo45Bq4VfR@debian.me> (raw)
In-Reply-To: <20220607142301.3eb8a53c@canb.auug.org.au>
On Tue, Jun 07, 2022 at 02:23:01PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hwmon-staging tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> Documentation/hwmon/lm90.rst:493: WARNING: Bullet list ends without a blank line; unexpected unindent.
> Documentation/hwmon/lm90.rst:494: WARNING: Bullet list ends without a blank line; unexpected unindent.
>
> Introduced by commit
>
> 7dd47c2603aa ("hwmon: (lm90) Support MAX1617 and LM84")
>
Hi Stephen,
These warnings above doesn't appear when doing htmldocs build using
Sphinx installed from pip on my system.
Cc-ing linux-doc list.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-07 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 4:23 linux-next: build warnings after merge of the hwmon-staging tree Stephen Rothwell
2022-06-07 9:35 ` Bagas Sanjaya [this message]
2022-06-07 12:39 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2024-02-04 23:41 Stephen Rothwell
2024-02-05 0:04 ` Guenter Roeck
2022-06-07 4:19 Stephen Rothwell
2022-06-07 9:37 ` Bagas Sanjaya
2022-06-07 12:40 ` Guenter Roeck
2021-11-24 5:22 Stephen Rothwell
2019-06-06 0:32 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=Yp8bz4Yo45Bq4VfR@debian.me \
--to=bagasdotme@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
/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).