From: Martin Kurbanov <mmkurbanov@sberdevices.ru>
To: Lee Jones <lee@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
<linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@sberdevices.ru>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: leds: add binding for aw200xx
Date: Thu, 16 Mar 2023 22:54:37 +0300 [thread overview]
Message-ID: <d0d9dbe3-ed4c-9212-e145-8fb8eee956ba@sberdevices.ru> (raw)
In-Reply-To: <20230316164031.GX9667@google.com>
On 2023-03-16 19:40, Lee Jones wrote:
> On Tue, 14 Mar 2023, Martin Kurbanov wrote:
>
>> Add YAML devicetree binding for AWINIC AW20036/AW20052/AW20074
>> led driver.
>>
>> Signed-off-by: Martin Kurbanov <mmkurbanov@sberdevices.ru>
>> ---
>> .../bindings/leds/awinic,aw200xx.yaml | 126 ++++++++++++++++++
>> 1 file changed, 126 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/leds/awinic,aw200xx.yaml
>
> Applied, thanks
>
> --
> Lee Jones [李琼斯]
Hello Lee,
Thank you for quick feedback! Sorry, I don't understand one thing.
Driver implementation from the patch series must be improved, so
currently it's not applied. Does dt bindings make sense without it?
I don't think so. Please fix me if I'm wrong.
--
Best Regards,
Kurbanov Martin
next prev parent reply other threads:[~2023-03-16 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 12:02 [PATCH v3 0/2] leds: add aw20xx driver Martin Kurbanov
2023-03-14 12:02 ` [PATCH v3 1/2] dt-bindings: leds: add binding for aw200xx Martin Kurbanov
2023-03-16 7:11 ` Krzysztof Kozlowski
2023-03-16 16:40 ` Lee Jones
2023-03-16 19:54 ` Martin Kurbanov [this message]
2023-03-17 8:09 ` Lee Jones
2023-03-14 12:02 ` [PATCH v3 2/2] leds: add aw20xx driver Martin Kurbanov
2023-03-14 12:12 ` Martin Kurbanov
2023-03-14 16:22 ` Andy Shevchenko
2023-03-14 16:49 ` Andy Shevchenko
2023-03-14 16:44 ` Andy Shevchenko
2023-03-15 9:59 ` kernel test robot
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=d0d9dbe3-ed4c-9212-e145-8fb8eee956ba@sberdevices.ru \
--to=mmkurbanov@sberdevices.ru \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@sberdevices.ru \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.