From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Akhil Raj <lf32.dev@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add leds-qcom-lpg to leds kernel docs tree
Date: Fri, 26 Aug 2022 19:49:26 +0700 [thread overview]
Message-ID: <28a70308-a996-7d97-430b-dc18bbd8bbcc@gmail.com> (raw)
In-Reply-To: <20220826081150.1961-1-lf32.dev@gmail.com>
On 8/26/22 15:11, Akhil Raj wrote:
> Warning was within
> ./Documentation/leds/leds-qcom-lpg.rst:
> WARNING: document isn't included in any toctree
>
> I have added leds-qcom-lpg to the index.rst
>
Hi,
Mauro had already submitted the same fix at [1]. Thanks anyway.
[1]: https://lore.kernel.org/linux-doc/14865c294b60fef58f660922889775bd57ce44c2.1660829433.git.mchehab@kernel.org/
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-08-26 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 8:11 [PATCH] Add leds-qcom-lpg to leds kernel docs tree Akhil Raj
2022-08-26 12:49 ` Bagas Sanjaya [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=28a70308-a996-7d97-430b-dc18bbd8bbcc@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=lf32.dev@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).