All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Bryan Wu <cooloney@gmail.com>
Cc: "rpurdie@rpsys.net" <rpurdie@rpsys.net>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	linux ARM <linux-arm-kernel@lists.infradead.org>,
	kaloz@openwrt.org, Matthew.Fatheree@belkin.com
Subject: Re: [PATCHv2 2/2] leds: tlc59116: Driver for the TI 16 Channel i2c LED driver
Date: Tue, 13 Jan 2015 20:13:49 +0100	[thread overview]
Message-ID: <20150113191349.GE14570@lunn.ch> (raw)
In-Reply-To: <CAK5ve-JQJJH_Dk=+PbFyRL3cjQUU4a5au4h9Kfcz6L6_iAfPKA@mail.gmail.com>

On Tue, Jan 13, 2015 at 10:55:23AM -0800, Bryan Wu wrote:
> On Fri, Jan 9, 2015 at 2:45 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> > The TLC59116 is an I2C bus controlled 16-channel LED driver.  Each LED
> > output has its own 8-bit fixed-frequency PWM controller to control the
> > brightness of the LED.
> >
> > This is based on a driver from Belkin, but has been extensively
> > rewritten.
> >
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > Cc: Matthew.Fatheree@belkin.com
> 
> Looks good, applied to my tree.

Great, thanks.

Will you also take the device tree binding document patch?

Thanks
	Andrew

WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/2] leds: tlc59116: Driver for the TI 16 Channel i2c LED driver
Date: Tue, 13 Jan 2015 20:13:49 +0100	[thread overview]
Message-ID: <20150113191349.GE14570@lunn.ch> (raw)
In-Reply-To: <CAK5ve-JQJJH_Dk=+PbFyRL3cjQUU4a5au4h9Kfcz6L6_iAfPKA@mail.gmail.com>

On Tue, Jan 13, 2015 at 10:55:23AM -0800, Bryan Wu wrote:
> On Fri, Jan 9, 2015 at 2:45 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> > The TLC59116 is an I2C bus controlled 16-channel LED driver.  Each LED
> > output has its own 8-bit fixed-frequency PWM controller to control the
> > brightness of the LED.
> >
> > This is based on a driver from Belkin, but has been extensively
> > rewritten.
> >
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > Cc: Matthew.Fatheree at belkin.com
> 
> Looks good, applied to my tree.

Great, thanks.

Will you also take the device tree binding document patch?

Thanks
	Andrew

  reply	other threads:[~2015-01-13 19:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 22:45 [PATCHv2 0/2] Driver for TI tlc59116 16 Channel i2c LED driver Andrew Lunn
2015-01-09 22:45 ` Andrew Lunn
2015-01-09 22:45 ` [PATCHv2 1/2] leds: tlc59116: Document binding for the TI " Andrew Lunn
2015-01-09 22:45   ` Andrew Lunn
2015-01-09 22:45 ` [PATCHv2 2/2] leds: tlc59116: Driver " Andrew Lunn
2015-01-09 22:45   ` Andrew Lunn
2015-01-13 18:55   ` Bryan Wu
2015-01-13 18:55     ` Bryan Wu
2015-01-13 19:13     ` Andrew Lunn [this message]
2015-01-13 19:13       ` Andrew Lunn
2015-01-13 19:18       ` Bryan Wu
2015-01-13 19:18         ` Bryan Wu
2015-01-13 19:28         ` Andrew Lunn
2015-01-13 19:28           ` Andrew Lunn
2015-01-13 19:39   ` Peter Meerwald
2015-01-13 19:57     ` Andrew Lunn
2015-01-13 20:04       ` 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=20150113191349.GE14570@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Matthew.Fatheree@belkin.com \
    --cc=cooloney@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kaloz@openwrt.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-leds@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.