From: Rob Herring <robh@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: mark.rutland@arm.com, jacek.anaszewski@gmail.com, pavel@ucw.cz,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt: bindings: lm3601x: Introduce the lm3601x driver
Date: Fri, 18 May 2018 10:11:43 -0500 [thread overview]
Message-ID: <20180518151143.GA13110@rob-hp-laptop> (raw)
In-Reply-To: <20180515154352.20263-1-dmurphy@ti.com>
On Tue, May 15, 2018 at 10:43:51AM -0500, Dan Murphy wrote:
> Introduce the device tree bindings for the lm3601x
> family of LED torch, flash and IR drivers.
>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
>
> v6 - Removed multiple led child nodes, fixed example to display micro ranges
> for corresponding child nodes and added led-sources to define the current driver -
> https://patchwork.kernel.org/patch/10392121/
>
> v5 - No changes - https://patchwork.kernel.org/patch/10391743/
> v4 - Added " " around "=", changed strobe to flash on label, removed "support and
> register" comment and change ir lable to ir:torch - See v2 patchworks for comments
> v3 - Removed wildcard compatible - https://patchwork.kernel.org/patch/10386241/
> v2 - No changes - https://patchwork.kernel.org/patch/10384587/
>
> .../devicetree/bindings/leds/leds-lm3601x.txt | 47 +++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3601x.txt
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2018-05-18 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 15:43 [PATCH v6 1/2] dt: bindings: lm3601x: Introduce the lm3601x driver Dan Murphy
2018-05-15 15:43 ` [PATCH v6 2/2] leds: lm3601x: Introduce the lm3601x LED driver Dan Murphy
2018-05-15 21:24 ` Jacek Anaszewski
2018-05-15 21:50 ` Dan Murphy
2018-05-16 20:43 ` Jacek Anaszewski
2018-05-15 21:56 ` Andy Shevchenko
2018-05-15 22:08 ` Dan Murphy
2018-05-15 22:24 ` Andy Shevchenko
2018-05-15 22:27 ` Andy Shevchenko
2018-05-16 20:43 ` Dan Murphy
2018-05-16 22:11 ` Andy Shevchenko
2018-05-16 22:19 ` Andy Shevchenko
2018-05-16 21:02 ` Jacek Anaszewski
2018-05-16 21:13 ` Dan Murphy
2018-05-16 21:17 ` Dan Murphy
2018-05-16 21:27 ` Jacek Anaszewski
2018-05-17 14:34 ` Dan Murphy
2018-05-17 21:26 ` Jacek Anaszewski
2018-05-15 21:13 ` [PATCH v6 1/2] dt: bindings: lm3601x: Introduce the lm3601x driver Jacek Anaszewski
2018-05-15 21:29 ` Dan Murphy
2018-05-16 20:10 ` Jacek Anaszewski
2018-05-16 20:14 ` Dan Murphy
2018-05-18 15:11 ` 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=20180518151143.GA13110@rob-hp-laptop \
--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=mark.rutland@arm.com \
--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