From: Rob Herring <robh@kernel.org>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>
Cc: Linux LED Subsystem <linux-leds@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, Dan Murphy <dmurphy@ti.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: leds: Convert common LED binding to schema
Date: Thu, 23 Jan 2020 15:20:26 -0600 [thread overview]
Message-ID: <CAL_Jsq+bOWJM5nvtY58+2DRtWQNzOPiVX9P===NOk4eBaE5OEA@mail.gmail.com> (raw)
In-Reply-To: <bec9ab4a-da09-6ef1-7334-d19f11ab2523@gmail.com>
On Wed, Jan 8, 2020 at 1:02 PM Jacek Anaszewski
<jacek.anaszewski@gmail.com> wrote:
>
> On 1/8/20 1:17 AM, Rob Herring wrote:
> > Convert the common LEDs properties bindings to a schema. As trigger source
> > providers are different nodes, we need to split trigger source properties
> > to a separate file.
> >
> > Bindings for LED controllers can reference the common schema for the LED
> > child nodes:
> >
> > patternProperties:
> > "^led@[0-4]":
> > type: object
> > allOf:
> > - $ref: common.yaml#
> >
> > Cc: Pavel Machek <pavel@ucw.cz>
> > Cc: Dan Murphy <dmurphy@ti.com>
> > Cc: linux-leds@vger.kernel.org
> > Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> > Signed-off-by: Rob Herring <robh@kernel.org>
> > ---
> > Jacek, Please take this via led tree
>
> Currently Pavel maintains LED tree. Pavel?
As it doesn't look like there's any conflicts, I've applied this
series to the DT tree.
Rob
next prev parent reply other threads:[~2020-01-23 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 0:17 [PATCH v2 1/2] dt-bindings: leds: Convert common LED binding to schema Rob Herring
2020-01-08 0:17 ` [PATCH v2 2/2] dt-bindings: leds: Convert gpio-leds to DT schema Rob Herring
2020-02-26 13:33 ` Pavel Machek
2023-01-17 12:32 ` Philippe Schenker
2020-01-08 19:02 ` [PATCH v2 1/2] dt-bindings: leds: Convert common LED binding to schema Jacek Anaszewski
2020-01-23 21:20 ` Rob Herring [this message]
2020-02-18 10:57 ` Pavel Machek
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='CAL_Jsq+bOWJM5nvtY58+2DRtWQNzOPiVX9P===NOk4eBaE5OEA@mail.gmail.com' \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).