The following changes since commit 4401e48737c4068604144a5c0ba23a9c82ea3a37:
leds: lp3944: Fix return value (2012-11-26 14:43:55 -0800)
are available in the git repository at:
git://git.linaro.org/people/sachin/linux-leds.git for-bryan
Sachin Kamat (16):
leds: leds-gpio: use devm_gpio_request_one
leds: leds-lt3593: use devm_gpio_request_one
leds: leds-ns2: use devm_gpio_request_one
leds: led-class: Fix checkpatch warning
leds: leds-adp5520: Fix checkpatch warnings
leds: leds-bd2802: Fix checkpatch warnings
leds: leds-da903x: Fix checkpatch error and warnings
leds: leds-gpio: Use dev_info instead of printk
leds: leds-lt3593: Fix checkpatch warnings
leds: leds-net48xx: Use linux/io.h instead of asm/io.h
leds: leds-pca955x: Use dev_info instead of printk
leds: leds-pwm: Fix checkpatch warning
leds: leds-wm8350: Use dev_err instead of printk
leds: leds-wrap: Use <linux/io.h> instead of <asm/io.h>
leds: ledtrig-backlight: Fix checkpatch error
leds: led-triggers: Fix checkpatch warnings
drivers/leds/led-class.c | 2 +-
drivers/leds/led-triggers.c | 12 ++++++------
drivers/leds/leds-adp5520.c | 4 ++--
drivers/leds/leds-bd2802.c | 6 +++---
drivers/leds/leds-da903x.c | 10 +++++-----
drivers/leds/leds-gpio.c | 10 +++-------
drivers/leds/leds-lt3593.c | 15 +++++----------
drivers/leds/leds-net48xx.c | 2 +-
drivers/leds/leds-ns2.c | 17 +++++------------
drivers/leds/leds-pca955x.c | 2 +-
drivers/leds/leds-pwm.c | 2 +-
drivers/leds/leds-wm8350.c | 4 ++--
drivers/leds/leds-wrap.c | 2 +-
drivers/leds/ledtrig-backlight.c | 2 +-
14 files changed, 37 insertions(+), 53 deletions(-)
On 27 November 2012 10:16, Sachin Kamat <sachin.kamat@xxxxxxxxxx> wrote:
> On 27 November 2012 04:02, Bryan Wu <cooloney@xxxxxxxxx> wrote:
>> On Sun, Nov 25, 2012 at 8:09 PM, Sachin Kamat <sachin.kamat@xxxxxxxxxx> wrote:
>>> This patch series is build tested against the for-next branch of following tree:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/linux-leds.git
>>>
>>
>> This is great for cleaning up. Thanks, Sachin.
>
> Thanks Bryan.
>>
>> Do you have a public git branch, where I can pull from? Otherwise I
>> need start to apply them manually.
>
> I have rebased the patches on top of your for-next branch and
> published them at the below location.
> Please let me know if you can pull from for-bryan branch of this git repo:
>
> git://git.linaro.org/people/sachin/linux-leds.git
>
>
>>
>> Thanks,
>> -Bryan
>>
>>> Sachin Kamat (16):
>>> leds: leds-gpio: use devm_gpio_request_one
>>> leds: leds-lt3593: use devm_gpio_request_one
>>> leds: leds-ns2: use devm_gpio_request_one
>>> leds: led-class: Fix checkpatch warning
>>> leds: leds-adp5520: Fix checkpatch warnings
>>> leds: leds-bd2802: Fix checkpatch warnings
>>> leds: leds-da903x: Fix checkpatch error and warnings
>>> leds: leds-gpio: Use dev_info instead of printk
>>> leds: leds-lt3593: Fix checkpatch warnings
>>> leds: leds-net48xx: Use linux/io.h instead of asm/io.h
>>> leds: leds-pca955x: Use dev_info instead of printk
>>> leds: leds-pwm: Fix checkpatch warning
>>> leds: leds-wm8350: Use dev_err instead of printk
>>> leds: leds-wrap: Use <linux/io.h> instead of <asm/io.h>
>>> leds: ledtrig-backlight: Fix checkpatch error
>>> leds: led-triggers: Fix checkpatch warnings
>>>
>>> drivers/leds/led-class.c | 2 +-
>>> drivers/leds/led-triggers.c | 12 ++++++------
>>> drivers/leds/leds-adp5520.c | 4 ++--
>>> drivers/leds/leds-bd2802.c | 6 +++---
>>> drivers/leds/leds-da903x.c | 10 +++++-----
>>> drivers/leds/leds-gpio.c | 10 +++-------
>>> drivers/leds/leds-lt3593.c | 15 +++++----------
>>> drivers/leds/leds-net48xx.c | 2 +-
>>> drivers/leds/leds-ns2.c | 17 +++++------------
>>> drivers/leds/leds-pca955x.c | 2 +-
>>> drivers/leds/leds-pwm.c | 2 +-
>>> drivers/leds/leds-wm8350.c | 4 ++--
>>> drivers/leds/leds-wrap.c | 2 +-
>>> drivers/leds/ledtrig-backlight.c | 2 +-
>>> 14 files changed, 37 insertions(+), 53 deletions(-)
>>>
>>> --
>>> 1.7.4.1
>>>
>
>
>
> --
> With warm regards,
> Sachin
--
With warm regards,
Sachin
--
To unsubscribe from this list: send the line "unsubscribe linux-leds" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
