From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Jonathan Corbet <corbet@lwn.net>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RESEND v2] leds: Add leds-qcom-lpg entry to documentation table of contents
Date: Sun, 12 Jun 2022 07:01:25 +0700 [thread overview]
Message-ID: <20220612000125.9777-1-bagasdotme@gmail.com> (raw)
After merging linux-leds tree to the mainline [1], htmldocs build produces
a new warning:
checking consistency... /home/bagas/repo/linux-stable/Documentation/leds/leds-qcom-lpg.rst: WARNING: document isn't included in any toctree
The warning above is because leds-qcom-lpg.rst is missing in the table of
contents.
Add the missing entry.
[1]: https://lore.kernel.org/all/20220531200619.GA8906@duo.ucw.cz/
Fixes: 24e2d05d1b6898 ("leds: Add driver for Qualcomm LPG")
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>
Cc: linux-leds@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/leds/index.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/leds/index.rst b/Documentation/leds/index.rst
index e5d63b9400459c..014e009b076159 100644
--- a/Documentation/leds/index.rst
+++ b/Documentation/leds/index.rst
@@ -25,4 +25,5 @@ LEDs
leds-lp5562
leds-lp55xx
leds-mlxcpld
+ leds-qcom-lpg
leds-sc27xx
base-commit: 0678afa6055d14799c1dc1eee47c8025eba56cab
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-06-12 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 0:01 Bagas Sanjaya [this message]
2022-06-13 17:42 ` [PATCH RESEND v2] leds: Add leds-qcom-lpg entry to documentation table of contents Jonathan Corbet
2022-06-28 0:33 ` Bagas Sanjaya
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=20220612000125.9777-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=pavel@ucw.cz \
/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).