linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Praghadeesh T K S <praghadeeshthevendria@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
	skhan@linuxfoundation.org, praghadeeshtks@zohomail.in
Subject: Re: [PATCH] docs: fix 'make htmldocs' warning in leds
Date: Tue, 28 Jun 2022 07:31:54 +0700	[thread overview]
Message-ID: <e2eee869-3e72-ea18-6afc-73fe5bc5dbd3@gmail.com> (raw)
In-Reply-To: <20220627214311.7817-1-praghadeeshthevendria@gmail.com>

On 6/28/22 04:43, Praghadeesh T K S wrote:
> Fix following 'make htmldocs' warnings:
> ./Documentation/leds/leds-qcom-lpg.rst: WARNING:
> document isn't included in any toctree
> 
> Signed-off-by: Praghadeesh T K S <praghadeeshthevendria@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 e5d63b9..b9ca081 100644
> --- a/Documentation/leds/index.rst
> +++ b/Documentation/leds/index.rst
> @@ -26,3 +26,4 @@ LEDs
>     leds-lp55xx
>     leds-mlxcpld
>     leds-sc27xx
> +   leds-qcom-lpg

Hi,

I had already sent the fix at [1] (resend at [2]). Thanks anyway.

[1]: https://lore.kernel.org/linux-doc/20220604015735.249707-1-bagasdotme@gmail.com/
[2]: https://lore.kernel.org/linux-doc/20220612000125.9777-1-bagasdotme@gmail.com/

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2022-06-28  0:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 21:43 [PATCH] docs: fix 'make htmldocs' warning in leds Praghadeesh T K S
2022-06-28  0:31 ` Bagas Sanjaya [this message]
2022-06-30 16:09   ` Praghadeesh T K S

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=e2eee869-3e72-ea18-6afc-73fe5bc5dbd3@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=praghadeeshthevendria@gmail.com \
    --cc=praghadeeshtks@zohomail.in \
    --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).