From: Lee Jones <lee@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Yi Xin <Yixin.zhu@intel.com>,
Mallikarjuna reddy <mallikarjunax.reddy@intel.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 2/2] dt-bindings: leds: Add missing references to common LED schema
Date: Thu, 8 Dec 2022 10:56:22 +0000 [thread overview]
Message-ID: <Y5HC1v7qk5K1M7k0@google.com> (raw)
In-Reply-To: <20221207204327.2810001-2-robh@kernel.org>
On Wed, 07 Dec 2022, Rob Herring wrote:
> 'led' nodes should have a reference to LED common.yaml schema. Add it where
> missing and drop any duplicate properties.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/leds/leds-lgm.yaml | 3 ++-
> .../devicetree/bindings/leds/leds-max77650.yaml | 9 ++-------
> .../bindings/leds/rohm,bd71828-leds.yaml | 16 +++-------------
> 3 files changed, 7 insertions(+), 21 deletions(-)
Acked-by: Lee Jones <lee@kernel.org>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2022-12-08 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 20:43 [PATCH 1/2] dt-bindings: leds: intel,lgm: Add missing 'led-gpios' property Rob Herring
2022-12-07 20:43 ` [PATCH 2/2] dt-bindings: leds: Add missing references to common LED schema Rob Herring
2022-12-08 9:28 ` Bartosz Golaszewski
2022-12-08 10:34 ` Krzysztof Kozlowski
2022-12-08 10:56 ` Lee Jones [this message]
2022-12-12 1:06 ` Rob Herring
2022-12-08 10:34 ` [PATCH 1/2] dt-bindings: leds: intel,lgm: Add missing 'led-gpios' property Krzysztof Kozlowski
2022-12-08 10:56 ` Lee Jones
2022-12-12 1:06 ` Rob Herring
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=Y5HC1v7qk5K1M7k0@google.com \
--to=lee@kernel.org \
--cc=Yixin.zhu@intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mallikarjunax.reddy@intel.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=pavel@ucw.cz \
--cc=robh@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.