public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Backlight updates
Date: Thu, 11 Oct 2007 22:38:11 +0100	[thread overview]
Message-ID: <1192138691.11368.11.camel@localhost.localdomain> (raw)

Linus,

Could you please pull from:

git://git.o-hand.com/linux-rpurdie-backlight for-linus

for the backlight tree updates for 2.6.24. This includes a new driver,
changes to an existing driver and some other fixes.

Thanks, Richard

 arch/arm/mach-pxa/corgi.c           |   18 +
 arch/arm/mach-pxa/spitz.c           |   18 +
 drivers/video/backlight/Kconfig     |   23 +-
 drivers/video/backlight/Makefile    |    2 
 drivers/video/backlight/backlight.c |    2 
 drivers/video/backlight/corgi_bl.c  |   22 +-
 drivers/video/backlight/cr_bllcd.c  |   35 ++-
 drivers/video/backlight/lcd.c       |    2 
 drivers/video/backlight/ltv350qv.c  |  330 ++++++++++++++++++++++++++++++++++++
 drivers/video/backlight/ltv350qv.h  |   95 ++++++++++
 include/asm-arm/arch-pxa/sharpsl.h  |    6 
 include/linux/backlight.h           |    9 
 12 files changed, 518 insertions(+), 44 deletions(-)

Adrian Bunk (1):
      backlight/leds: Make two structs static

Haavard Skinnemoen (1):
      backlight: Add Samsung LTV350QV LCD driver

Jesper Juhl (1):
      backlight: Fix cr_bllcd allocations and error paths

Richard Purdie (1):
      backlight: Convert corgi backlight driver into a more generic driver



             reply	other threads:[~2007-10-11 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 21:38 Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-07 10:37 [GIT PULL] Backlight updates Richard Purdie
2007-07-16  8:39 Richard Purdie
2007-03-05 12:59 Richard Purdie
2007-02-20 13:06 Richard Purdie

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=1192138691.11368.11.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --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