From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ChiYuan Huang <cy_huang@richtek.com>,
ChiaEn Wu <chiaen_wu@richtek.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the leds-lj tree
Date: Thu, 23 Mar 2023 15:14:38 +0000 [thread overview]
Message-ID: <20230323151438.GO2673958@google.com> (raw)
In-Reply-To: <20230323142904.1a136fdf@canb.auug.org.au>
On Thu, 23 Mar 2023, Stephen Rothwell wrote:
> Hi all,
>
> After merging the leds-lj tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> Documentation/leds/leds-mt6370-rgb.rst: WARNING: document isn't included in any toctree
> Documentation/leds/leds-mt6370-rgb.rst:39: WARNING: Literal block ends without a blank line; unexpected unindent.
> Documentation/leds/leds-mt6370-rgb.rst:41: WARNING: Line block ends without a blank line.
> Documentation/leds/leds-mt6370-rgb.rst:46: ERROR: Unexpected indentation.
> Documentation/leds/leds-mt6370-rgb.rst:44: WARNING: Inline substitution_reference start-string without end-string.
> Documentation/leds/leds-mt6370-rgb.rst:50: WARNING: Literal block expected; none found.
What wizardry is this?
> Introduced by commit
>
> 4ba9df04b7ac ("docs: leds: Add MT6370 RGB LED pattern document")
There is a fixing set on the list that I need to review.
Please bear with me.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-03-23 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 3:29 linux-next: build warnings after merge of the leds-lj tree Stephen Rothwell
2023-03-23 15:14 ` Lee Jones [this message]
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=20230323151438.GO2673958@google.com \
--to=lee@kernel.org \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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