From: Samuel Ortiz <sameo@linux.intel.com>
To: Richard Purdie <rpurdie@linux.intel.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] gta02: Use pcf50633 backlight driver instead of platform backlight driver.
Date: Mon, 17 May 2010 00:00:11 +0200 [thread overview]
Message-ID: <20100516220010.GA3236@sortiz.org> (raw)
In-Reply-To: <1273760705.12731.12.camel@rex>
Hi Richard,
On Thu, May 13, 2010 at 10:25:05PM +0800, Richard Purdie wrote:
> On Wed, 2010-05-12 at 02:02 +0100, Ben Dooks wrote:
> > On Wed, May 12, 2010 at 02:44:34AM +0200, Lars-Peter Clausen wrote:
> > > Use the pcf50633 backlight driver instead of the platform backlight driver.
> > >
> > > Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> > > Cc: Ben Dooks <ben-linux@fluff.org>
> >
> > ok, does anyone else have a comment on this?
>
> Looks like a sensible idea to me but I'm travelling and don't have time
> to properly review the patches right now.
>
> The main question is who takes which patches. I can take the main new
> backlight one, the other two I need opinions from the mfd (Samuel) and
> gta02 (?) maintainers...
The MFD patch looks good to me, you can add my:
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Cheers,
Samuel.
> Cheers,
>
> Richard
>
>
>
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-05-16 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 0:44 [PATCH 0/3] Add pcf50633 " Lars-Peter Clausen
2010-05-12 0:44 ` [PATCH 1/3] backlight: " Lars-Peter Clausen
2010-05-12 0:44 ` [PATCH 2/3] MFD: pcf50633: Register a pcf50633-backlight device in pcf50633 core driver Lars-Peter Clausen
2010-05-12 0:44 ` [PATCH 3/3] gta02: Use pcf50633 backlight driver instead of platform backlight driver Lars-Peter Clausen
2010-05-12 1:02 ` Ben Dooks
2010-05-13 14:25 ` Richard Purdie
2010-05-16 22:00 ` Samuel Ortiz [this message]
2010-05-26 11:57 ` 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=20100516220010.GA3236@sortiz.org \
--to=sameo@linux.intel.com \
--cc=ben-linux@fluff.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@linux.intel.com \
/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
Powered by JetHome