linux-kernel - Re: [PATCH RESEND v2] leds: Add leds-qcom-lpg entry to documentation table of contents

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87v8t4zcht.fsf@meer.lwn.net>
Date:   Mon, 13 Jun 2022 11:42:22 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Bagas Sanjaya <bagasdotme@...il.com>, linux-doc@...r.kernel.org
Cc:     Bagas Sanjaya <bagasdotme@...il.com>, Pavel Machek <pavel@....cz>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Marijn Suijten <marijn.suijten@...ainline.org>,
        linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v2] leds: Add leds-qcom-lpg entry to
 documentation table of contents

Bagas Sanjaya <bagasdotme@...il.com> writes:

> 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@....cz>
> Cc: Jonathan Corbet <corbet@....net>
> Cc: Bjorn Andersson <bjorn.andersson@...aro.org>
> Cc: Marijn Suijten <marijn.suijten@...ainline.org>
> Cc: linux-leds@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>

Pavel, that document appears to have entered via your tree; do you plan
to push this fix too?

Thanks,

jon