From: Rob Herring <robh@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: mark.rutland@arm.com, rpurdie@rpsys.net,
jacek.anaszewski@gmail.com, pavel@ucw.cz,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v5 4/6] dt: bindings: lp8860: Add trigger binding to the lp8860
Date: Wed, 20 Dec 2017 12:29:11 -0600 [thread overview]
Message-ID: <20171220182911.ivsr6uzf5vq6clkh@rob-hp-laptop> (raw)
In-Reply-To: <20171218202307.4913-4-dmurphy@ti.com>
On Mon, Dec 18, 2017 at 02:23:05PM -0600, Dan Murphy wrote:
> Add a default trigger optional node to the child node.
> This will allow the driver to set the trigger for a backlight.
>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
>
> v5 - No changes
>
> v4 - No changes
> v3 - Removed optional and rebased - https://patchwork.kernel.org/patch/10093755/
> v2 - Moved binding changes to first patch in the series.
>
> Documentation/devicetree/bindings/leds/leds-lp8860.txt | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-12-20 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 20:23 [PATCH v5 1/6] dt: bindings: lp8860: Update bindings for lp8860 Dan Murphy
2017-12-18 20:23 ` [PATCH v5 4/6] dt: bindings: lp8860: Add trigger binding to the lp8860 Dan Murphy
2017-12-20 18:29 ` Rob Herring [this message]
2017-12-18 20:23 ` [PATCH v5 5/6] leds: lp8860: Add DT parsing to retrieve the trigger node Dan Murphy
[not found] ` <20171218202307.4913-1-dmurphy-l0cyMroinI0@public.gmane.org>
2017-12-18 20:23 ` [PATCH v5 2/6] dt: bindings: lp8860: Update DT label binding Dan Murphy
2017-12-20 18:28 ` Rob Herring
2017-12-18 20:23 ` [PATCH v5 3/6] leds: lp8860: Update the dt parsing for LED labeling Dan Murphy
2017-12-18 20:23 ` [PATCH v5 6/6] leds: lp8860: Various fixes to align with LED framework Dan Murphy
2017-12-19 20:20 ` [PATCH v5 1/6] dt: bindings: lp8860: Update bindings for lp8860 Jacek Anaszewski
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=20171220182911.ivsr6uzf5vq6clkh@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 \
--cc=rpurdie@rpsys.net \
/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).