From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Lee Jones <lee@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
jacek.anaszewski@gmail.com, pavel@ucw.cz, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
thunder.leizhen@huawei.com, festevam@gmail.com
Subject: Re: [PATCH v4] dt-bindings: leds: Document commonly used LED triggers
Date: Tue, 7 Feb 2023 21:39:15 +0100 [thread overview]
Message-ID: <639db6ae-c7de-eec2-de4f-516aba471d47@linaro.org> (raw)
In-Reply-To: <Y+KcndmBBQw16hfM@google.com>
On 07/02/2023 19:46, Lee Jones wrote:
> On Tue, 07 Feb 2023, Krzysztof Kozlowski wrote:
>
>> On 29/11/2022 18:49, Manivannan Sadhasivam wrote:
>>> Document the commonly used LED triggers by the SoCs. Not all triggers
>>> are documented as some of them are very application specific. Most of the
>>> triggers documented here are currently used in devicetrees of many SoCs.
>>>
>>> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>>> ---
>>>
>>> Changes in v4:
>>>
>>> * Removed the sorting of triggers
>>> * Removed the "items" as they were not needed
>>> * Reworded the description
>>> * Dropped Zhen Lei's tested-by tag as the patch has changed
>>> * Added kbd-capslock trigger
>>
>> Any plans for this patch?
>
> Who are you asking?
>
> This patch is not in my inbox.
Mani and Pavel. I Cc-ed you just for completeness.
I would expect Mani to rebase and resend it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-07 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 17:49 [PATCH v4] dt-bindings: leds: Document commonly used LED triggers Manivannan Sadhasivam
2022-11-30 0:35 ` Rob Herring
2023-02-07 11:33 ` Krzysztof Kozlowski
2023-02-07 18:46 ` Lee Jones
2023-02-07 20:39 ` Krzysztof Kozlowski [this message]
2023-02-07 21:39 ` Lee Jones
2023-02-13 7:09 ` Manivannan Sadhasivam
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=639db6ae-c7de-eec2-de4f-516aba471d47@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jacek.anaszewski@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=thunder.leizhen@huawei.com \
/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).