From: Lee Jones <lee@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux MediaTek <linux-mediatek@lists.infradead.org>,
Linux LEDs <linux-leds@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Shuah Khan <skhan@linuxfoundation.org>,
ChiaEn Wu <chiaen_wu@richtek.com>,
ChiYuan Huang <cy_huang@richtek.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 2/3] Documentation: leds: MT6370: Properly wrap hw_pattern chart
Date: Thu, 23 Mar 2023 15:17:33 +0000 [thread overview]
Message-ID: <20230323151733.GQ2673958@google.com> (raw)
In-Reply-To: <20230319074903.13075-3-bagasdotme@gmail.com>
On Sun, 19 Mar 2023, Bagas Sanjaya wrote:
> The pattern diagram (chart) of /sys/class/leds/<led>/hw_pattern is
> wrapped in literal code block. However, the block indentation is
> interrupted by Icurr axis label, hence below warnings:
>
> 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: WARNING: Unexpected indentation.
> Documentation/leds/leds-mt6370-rgb.rst:44: WARNING: Inline substitution_reference start-string without end-string.
>
> Fix the chart indentation by adding 4 more spaces so that the axis label
> is in the code block.
>
> Link: https://lore.kernel.org/oe-kbuild-all/202303182310.tB1mUzU7-lkp@intel.com/
> Fixes: 4ba9df04b7ac66 ("docs: leds: Add MT6370 RGB LED pattern document")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/leds/leds-mt6370-rgb.rst | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
Applied, thanks
--
Lee Jones [李琼斯]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-23 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 7:49 [PATCH 0/3] Documentation fixes for MT6370 RGB Bagas Sanjaya
2023-03-19 7:49 ` [PATCH 1/3] Documentation: leds: Add MT6370 doc to the toctree Bagas Sanjaya
2023-03-23 15:16 ` Lee Jones
2023-03-19 7:49 ` [PATCH 2/3] Documentation: leds: MT6370: Properly wrap hw_pattern chart Bagas Sanjaya
2023-03-23 15:17 ` Lee Jones [this message]
2023-03-19 7:49 ` [PATCH 3/3] Documentation: leds: MT6370: Use bullet lists for timing variables Bagas Sanjaya
2023-03-23 15:18 ` Lee Jones
2023-03-23 5:06 ` [PATCH 0/3] Documentation fixes for MT6370 RGB Bagas Sanjaya
2023-03-23 12:31 ` Lee Jones
2023-03-23 12:35 ` Bagas Sanjaya
2023-03-23 11:08 ` Pavel Machek
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=20230323151733.GQ2673958@google.com \
--to=lee@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bagasdotme@gmail.com \
--cc=chiaen_wu@richtek.com \
--cc=corbet@lwn.net \
--cc=cy_huang@richtek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=skhan@linuxfoundation.org \
/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).