From: Pavel Machek <pavel@ucw.cz>
To: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sven Schwermer <sven.schwermer@disruptive-technologies.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: leds: pwm-multicolor: document max-brigthness
Date: Sat, 30 Jul 2022 23:00:29 +0200 [thread overview]
Message-ID: <20220730210029.GC23307@duo.ucw.cz> (raw)
In-Reply-To: <20220719232614.GA2034561-robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Tue 2022-07-19 17:26:14, Rob Herring wrote:
> On Tue, 19 Jul 2022 09:45:42 +0200, Krzysztof Kozlowski wrote:
> > The Multicolor PWM LED uses max-brigthness property (in the example and
> > in the driver), so document it to fixi dt_binding_check warning like:
> >
> > leds/leds-pwm-multicolor.example.dtb:
> > led-controller: multi-led: Unevaluated properties are not allowed ('max-brightness' was unexpected)
> >
> > Reported-by: Rob Herring <robh@kernel.org>
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > ---
> > .../devicetree/bindings/leds/leds-pwm-multicolor.yaml | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thank you, applied.
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-07-30 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 7:45 [PATCH] dt-bindings: leds: pwm-multicolor: document max-brigthness Krzysztof Kozlowski
2022-07-19 23:26 ` Rob Herring
2022-07-30 21:00 ` Pavel Machek [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=20220730210029.GC23307@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sven.schwermer@disruptive-technologies.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).