From: jochen@scram.de (Jochen Friedrich)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3.1 0/4] ARM: simpad: Add support for GPIO attached hardware
Date: Sun, 07 Aug 2011 22:10:35 +0200 [thread overview]
Message-ID: <4E3EF13B.5020003@scram.de> (raw)
In-Reply-To: <20110807200500.GC2588@Boggieman>
Am 07.08.2011 22:05, schrieb Kristoffer Ericson:
> n Wed, Aug 03, 2011 at 12:40:05PM +0200, Jochen Friedrich wrote:
>> Hi Bryan,
>>
>>> Is there any news about this patchset? Merged already? I'm going to
>>> post an updated Led patchset based on this.
>>
>> Not yet. I'm currently waiting for the end of the merge window prior
>> to submitting this patch against 3.1-rc1 again.
>
> You still havent gotten any reply about those patches? I know Ive been
> occupied lately but I could give them a look/apply if that helps.
I got a few comments which I hope to have addressed, but not yet the OK from Alan to add them to his patch tracking system.
Thanks,
Jochen
next prev parent reply other threads:[~2011-08-07 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 6:46 [PATCH 3.1 0/4] ARM: simpad: Add support for GPIO attached hardware Jochen Friedrich
2011-07-12 6:46 ` [PATCH 3.1 1/4] ARM:simpad: Add ucb1x00 GPIO definitions and register GPIO Jochen Friedrich
2011-07-12 6:46 ` [PATCH 3.1 2/4] ARM:simpad: Cleanup CS3 accessors Jochen Friedrich
2011-07-12 6:46 ` [PATCH 3.1 3/4] ARM:simpad: add GPIO based device definitions Jochen Friedrich
2011-07-12 7:32 ` Dmitry Eremin-Solenikov
2011-07-13 12:38 ` Jochen Friedrich
2011-07-13 12:40 ` Dmitry Eremin-Solenikov
2011-07-12 6:46 ` [PATCH 3.1 4/4] ARM: simpad: replace ARM specific LED code Jochen Friedrich
2011-08-03 3:47 ` [PATCH 3.1 0/4] ARM: simpad: Add support for GPIO attached hardware Bryan Wu
2011-08-03 10:40 ` Jochen Friedrich
2011-08-07 20:05 ` Kristoffer Ericson
2011-08-07 20:10 ` Jochen Friedrich [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-06 14:42 Jochen Friedrich
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=4E3EF13B.5020003@scram.de \
--to=jochen@scram.de \
--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).