From: Bryan Wu <cooloney@gmail.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>,
"Linux LED Subsystem" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
jogo@openwrt.org, "Florian Fainelli" <f.fainelli@gmail.com>,
cernekee@gmail.com
Subject: Re: [PATCH v2 1/2] leds: add DT binding for BCM6358 LED controller
Date: Fri, 22 May 2015 15:32:49 -0700 [thread overview]
Message-ID: <CAK5ve-JvCAL6_ZhCGH7yAnufPH9mTBChRwkmk2k+G-UN4ovExQ@mail.gmail.com> (raw)
In-Reply-To: <555F468A.6030907@samsung.com>
On Fri, May 22, 2015 at 8:08 AM, Jacek Anaszewski
<j.anaszewski@samsung.com> wrote:
> On 05/21/2015 07:11 PM, Álvaro Fernández Rojas wrote:
>>
>> This adds device tree binding documentation for the Broadcom BCM6358 LED
>> controller.
>>
>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>> ---
>> v2: resend, no changes.
>>
>> .../devicetree/bindings/leds/leds-bcm6358.txt | 145
>> +++++++++++++++++++++
>> 1 file changed, 145 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/leds/leds-bcm6358.txt
>
>
> Acked-by: Jacek Anaszewski <j.anaszewski@samsung.com>
>
Applied, thanks.
-Bryan
next prev parent reply other threads:[~2015-05-22 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 17:12 [PATCH 0/2] BCM6358 LED driver Álvaro Fernández Rojas
2015-05-19 17:12 ` [PATCH 1/2] leds: add DT binding for BCM6358 LED controller Álvaro Fernández Rojas
2015-05-21 11:01 ` Jacek Anaszewski
2015-05-19 17:12 ` [PATCH 2/2] leds: add BCM6358 LED driver Álvaro Fernández Rojas
2015-05-21 10:58 ` Jacek Anaszewski
2015-05-21 17:11 ` [PATCH v2 0/2] " Álvaro Fernández Rojas
2015-05-21 17:11 ` [PATCH v2 1/2] leds: add DT binding for BCM6358 LED controller Álvaro Fernández Rojas
2015-05-22 15:08 ` Jacek Anaszewski
2015-05-22 22:32 ` Bryan Wu [this message]
2015-05-21 17:11 ` [PATCH v2 2/2] leds: add BCM6358 LED driver Álvaro Fernández Rojas
2015-05-22 15:10 ` Jacek Anaszewski
2015-05-22 22:34 ` Bryan Wu
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=CAK5ve-JvCAL6_ZhCGH7yAnufPH9mTBChRwkmk2k+G-UN4ovExQ@mail.gmail.com \
--to=cooloney@gmail.com \
--cc=cernekee@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=jogo@openwrt.org \
--cc=linux-leds@vger.kernel.org \
--cc=noltari@gmail.com \
/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).