From: Riku Voipio <riku.voipio@iki.fi>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: rpurdie@rpsys.net, 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 23:46:49 +0300 [thread overview]
Message-ID: <20080429204649.GA23817@kos.to> (raw)
In-Reply-To: <20080429132631.e0dc7803.akpm@linux-foundation.org>
On Tue, Apr 29, 2008 at 01:26:31PM -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/...
Since it depends on pca9532-led-driver being added first, I believe
it would logistically simpler to get both patches through leds tree.
--
"rm -rf" only sounds scary if you don't have backups
next prev parent reply other threads:[~2008-04-29 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 20:08 [PATCH] Add pca9532 platform data for Thecus N2100 Riku Voipio
2008-04-29 20:26 ` Andrew Morton
2008-04-29 20:45 ` Richard Purdie
2008-04-29 20:55 ` Russell King
2008-04-29 20:46 ` Riku Voipio [this message]
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=20080429204649.GA23817@kos.to \
--to=riku.voipio@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=buytenh@wantstofly.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--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 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.