From: Richard Purdie <rpurdie@rpsys.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] LED updates for 2.6.31
Date: Tue, 23 Jun 2009 20:29:19 +0100 [thread overview]
Message-ID: <1245785359.26606.13.camel@dax.rpnet.com> (raw)
Linus,
Could you please pull from:
git://git.o-hand.com/linux-rpurdie-leds for-linus
for the LED tree updates for 2.6.31. This is mainly minor
bugfixes/cleanups and also one new driver.
Thanks, Richard
Documentation/leds-lp3944.txt | 50 ++
Documentation/powerpc/dts-bindings/gpio/led.txt | 17
drivers/leds/Kconfig | 14
drivers/leds/Makefile | 1
drivers/leds/leds-alix2.c | 7
drivers/leds/leds-bd2802.c | 96 +++-
drivers/leds/leds-gpio.c | 22 -
drivers/leds/leds-lp3944.c | 466 ++++++++++++++++++++++++
drivers/leds/leds-pca9532.c | 58 +-
include/linux/leds-lp3944.h | 53 ++
include/linux/leds.h | 14
11 files changed, 733 insertions(+), 65 deletions(-)
Antonio Ospite (2):
leds: pca9532 - Indent using tabs, not spaces.
leds: LED driver for National Semiconductor LP3944 Funlight Chip
Kim Kyuwon (3):
leds: fix led-bd2802 errors while resuming
leds: change the license information
leds: add the sysfs interface into the leds-bd2802 driver for changing wave pattern and led current.
Mark Brown (1):
leds: Further document parameters for blink_set()
Richard Purdie (2):
leds: Remove an orphan Kconfig entry
leds: Futher document blink_set
Tobias Mueller (1):
leds: alix-leds2 fixed for Award BIOS
Trent Piepho (1):
leds: Add options to have GPIO LEDs start on or keep their state
Zhenwen Xu (1):
leds: leds-gpio - fix a section mismatch
--
Richard Purdie
Intel Open Source Technology Centre
reply other threads:[~2009-06-23 19:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1245785359.26606.13.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®