From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 2.6.40 0/4] ARM: simpad: Add support for GPIO attached hardware
Date: Thu, 28 Apr 2011 10:24:17 +0100 [thread overview]
Message-ID: <20110428092417.GS17290@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1303377543-24794-1-git-send-email-jochen@scram.de>
On Thu, Apr 21, 2011 at 11:18:59AM +0200, Jochen Friedrich wrote:
> This series enables GPIO API on UCB1x00 and implements the GPIO
> API on the CS3 latch. The third patch finally registers platform
> devices for the GPIO attached LED, buttons and I2C bus.
>
> v2: In response to the Linus rant, remove the ARM specific LED
> support for simpad hardware instead of supporting it
> alternatively to the generic LED code.
>
> v3: Move LED changes into a seperate patch.
>
> ARM: simpad: Add ucb1x00 GPIO definitions and register GPIO
> ARM: simpad: Cleanup CS3 accessors and add GPIO API
> ARM: simpad: add GPIO based device definitions
> ARM: simpad: replace ARM specific LED code
It would be useful to provide the overall diffstat for this set of changes,
so we can see what the effect of all patches together are.
prev parent reply other threads:[~2011-04-28 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 9:18 [PATCHv3 2.6.40 0/4] ARM: simpad: Add support for GPIO attached hardware Jochen Friedrich
2011-04-21 9:19 ` [PATCHv3 2.6.40 1/4] ARM: simpad: Add ucb1x00 GPIO definitions and register GPIO Jochen Friedrich
2011-04-21 9:19 ` [PATCHv3 2.6.40 2/4] ARM: simpad: Cleanup CS3 accessors Jochen Friedrich
2011-04-28 9:23 ` Russell King - ARM Linux
2011-04-29 14:38 ` Jochen Friedrich
2011-04-21 9:19 ` [PATCHv3 2.6.40 3/4] ARM: simpad: add GPIO based device definitions Jochen Friedrich
2011-04-21 9:19 ` [PATCHv3 2.6.40 4/4] ARM: simpad: replace ARM specific LED code Jochen Friedrich
2011-04-28 9:24 ` Russell King - ARM Linux [this message]
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=20110428092417.GS17290@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).