All of lore.kernel.org
 help / color / mirror / Atom feed
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.32
Date: Sat, 26 Sep 2009 17:10:51 +0100	[thread overview]
Message-ID: <1253981451.7598.61.camel@ted> (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.32. This is mainly minor
bugfixes/cleanups and also one new driver.

Thanks, Richard

 drivers/leds/Kconfig              |   13 +-
 drivers/leds/Makefile             |    1 +
 drivers/leds/leds-clevo-mail.c    |    2 +-
 drivers/leds/leds-cobalt-qube.c   |    2 +-
 drivers/leds/leds-cobalt-raq.c    |    4 +-
 drivers/leds/leds-gpio.c          |    2 +-
 drivers/leds/leds-pca9532.c       |   12 +-
 drivers/leds/leds-wm831x-status.c |  341 +++++++++++++++++++++++++++++++++++++
 drivers/leds/ledtrig-gpio.c       |   28 ++--
 drivers/macintosh/via-pmu-led.c   |    2 +-
 include/linux/mfd/wm831x/status.h |   34 ++++
 11 files changed, 412 insertions(+), 29 deletions(-)
 create mode 100644 drivers/leds/leds-wm831x-status.c
 create mode 100644 include/linux/mfd/wm831x/status.h

Antonio Ospite (1):
      leds: Fix indentation in LEDS_LP3944 Kconfig entry

Mark Brown (1):
      leds: Add WM831x status LED driver

Michal Simek (1):
      leds: gpio-leds: fix typographics fault

Olaf Hering (1):
      leds: Fix LED names

Richard Purdie (1):
      leds: Fix leds-pca9532 whitespace issues

Thadeu Lima de Souza Cascardo (1):
      leds: fix coding style in worker thread code for ledtrig-gpio.

Uwe Kleine-König (1):
      leds: move leds-clevo-mail's probe function to .devinit.text


-- 
Richard Purdie
Intel Open Source Technology Centre


                 reply	other threads:[~2009-09-26 16:11 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=1253981451.7598.61.camel@ted \
    --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 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.