From: Richard Purdie <rpurdie@rpsys.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Riku Voipio <riku.voipio@iki.fi>,
linux-kernel@vger.kernel.org, buytenh@wantstofly.org,
tbm@cyrius.com, Russell King <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] Add pca9532 platform data for Thecus N2100
Date: Tue, 29 Apr 2008 21:45:31 +0100 [thread overview]
Message-ID: <1209501931.5642.47.camel@dax.rpnet.com> (raw)
In-Reply-To: <20080429132631.e0dc7803.akpm@linux-foundation.org>
On Tue, 2008-04-29 at 13:26 -0700, Andrew Morton wrote:
> On Tue, 29 Apr 2008 23:08:53 +0300
> Riku Voipio <riku.voipio@iki.fi> wrote:
>
> > Thecus N2100 has leds and a buzzer attached to a pca9532
> > controller. Attach the driver to the i2c bus and define
> > the pca9532 pin coniguration for this platform in n2100_leds.
> >
> > With this patch, support for N2100 should be complete in mainline
> > Linux.
> >
> > Signed-off-by: Riku Voipio <riku.voipio@iki.fi>
> > ---
> > arch/arm/mach-iop32x/n2100.c | 52 ++++++++++++++++++++++++++++++++++++++++++
> > 1 files changed, 52 insertions(+), 0 deletions(-)
>
> So I guess this is really a patch for the git-leds tree, even though
> it affects only arch/arm/...
Acked-by: Richard Purdie <rpurdie@rpsys.net>
I'll await guidance from Russell about where he wants it to go, I'm fine
with git-leds but if he wants to take it through the arm tree I'm ok
with that too in which case the ACK above applies.
Cheers,
Richard
next prev parent reply other threads:[~2008-04-29 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 20:08 Riku Voipio
2008-04-29 20:26 ` Andrew Morton
2008-04-29 20:45 ` Richard Purdie [this message]
2008-04-29 20:55 ` Russell King
2008-04-29 20:46 ` Riku Voipio
2008-04-29 20:56 ` Russell King
2008-04-29 21:16 ` Richard Purdie
2008-04-30 6:26 ` Lennert Buytenhek
2008-04-30 7:50 ` Mikael Pettersson
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=1209501931.5642.47.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=akpm@linux-foundation.org \
--cc=buytenh@wantstofly.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@iki.fi \
--cc=rmk@arm.linux.org.uk \
--cc=tbm@cyrius.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
all inboxes | Powered by JetHome®