devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: sven@svenschwermer.de
Cc: linux-pwm@vger.kernel.org, post@lespocky.de,
	linux-leds@vger.kernel.org, andy.shevchenko@gmail.com,
	devicetree@vger.kernel.org, thierry.reding@gmail.com,
	pavel@ucw.cz, u.kleine-koenig@pengutronix.de,
	Sven Schwermer <sven.schwermer@disruptive-technologies.com>,
	robh+dt@kernel.org, lee.jones@linaro.org
Subject: Re: [PATCH v6 1/3] dt-bindings: leds: Optional multi-led unit address
Date: Wed, 9 Feb 2022 12:35:37 -0600	[thread overview]
Message-ID: <YgQJeXKnQrWjjzcI@robh.at.kernel.org> (raw)
In-Reply-To: <20220208191236.660172-1-sven@svenschwermer.de>

On Tue, 08 Feb 2022 20:12:34 +0100, sven@svenschwermer.de wrote:
> From: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
> 
> The unit address does not make sense in all cases the multi-led node is
> used, e.g. for the upcoming PWM multi-color LED driver.
> 
> Signed-off-by: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
> ---
> 
> Notes:
>     Added in v6
> 
>  .../devicetree/bindings/leds/leds-class-multicolor.yaml         | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

      parent reply	other threads:[~2022-02-09 18:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 19:12 [PATCH v6 1/3] dt-bindings: leds: Optional multi-led unit address sven
2022-02-08 19:12 ` [PATCH v6 2/3] dt-bindings: leds: Add multicolor PWM LED bindings sven
2022-02-09  9:17   ` Alexander Dahl
2022-02-10  7:55     ` Sven Schwermer
2022-02-10  9:33       ` Alexander Dahl
2022-02-11 19:37         ` Sven Schwermer
2022-02-09 18:44   ` Rob Herring
2022-02-08 19:12 ` [PATCH v6 3/3] leds: Add PWM multicolor driver sven
2022-02-09 18:35 ` Rob Herring [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=YgQJeXKnQrWjjzcI@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=post@lespocky.de \
    --cc=robh+dt@kernel.org \
    --cc=sven.schwermer@disruptive-technologies.com \
    --cc=sven@svenschwermer.de \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).