From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] gpio: rewrite U300 GPIO to use gpiolib
Date: Wed, 7 Sep 2011 22:02:04 -0700 [thread overview]
Message-ID: <CACxGe6vp7FS3YqOB2QUg+k-qC5t8sGFDjwJb1GSqxuV+BFWE-w@mail.gmail.com> (raw)
In-Reply-To: <20110907180207.GC9937@ponder.secretlab.ca>
On Wed, Sep 7, 2011 at 11:02 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Wed, Sep 07, 2011 at 10:11:25AM +0200, Linus Walleij wrote:
>> From: Linus Walleij <linus.walleij@linaro.org>
>>
>> This rewrites the U300 GPIO so as to use gpiolib and
>> struct gpio_chip instead of just generic GPIO, hiding
>> all the platform specifics and passing in GPIO chip
>> variant as platform data at runtime instead of the
>> compiletime kludges.
>>
>> As a result <mach/gpio.h> is now empty for U300 and
>> using just defaults.
>>
>> Cc: Russell King <linux@arm.linux.org.uk>
>> Cc: Grant Likely <grant.likely@secretlab.ca>
>> Cc: Debian kernel maintainers <debian-kernel@lists.debian.org>
>> Cc: Arnaud Patard <arnaud.patard@rtp-net.org>
>> Reported-by: Ben Hutchings <ben@decadent.org.uk>
>> Signed-off-nu: Linus Walleij <linus.walleij@linaro.org>
> ? ? ? ? ? ? ^^
> Your keyboard needs to be shifted 1cm to the right. :-)
>
> I'll pick it up, but there are some things that I've commented on
> below that needs to be addressed in follow up patches.
Hmmm, it doesn't apply against mainline. Do you want to take it
through your tree?
g.
next prev parent reply other threads:[~2011-09-08 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 8:11 [PATCH v2] gpio: rewrite U300 GPIO to use gpiolib Linus Walleij
2011-09-07 12:55 ` Barry Song
2011-09-07 19:23 ` Linus Walleij
2011-09-07 18:02 ` Grant Likely
2011-09-08 5:02 ` Grant Likely [this message]
2011-09-08 8:01 ` Linus Walleij
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=CACxGe6vp7FS3YqOB2QUg+k-qC5t8sGFDjwJb1GSqxuV+BFWE-w@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).