From: dbaryshkov@gmail.com (Dmitry Eremin-Solenikov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3.1 3/4] ARM:simpad: add GPIO based device definitions.
Date: Wed, 13 Jul 2011 16:40:58 +0400 [thread overview]
Message-ID: <4E1D925A.9050601@gmail.com> (raw)
In-Reply-To: <4E1D91CB.6090405@scram.de>
Hello,
On 13.07.2011 16:38, Jochen Friedrich wrote:
> Hi Dmitry,
>
>>> @@ -259,7 +321,10 @@ static struct platform_device simpad_mq200fb = {
>>> };
>>>
>>> static struct platform_device *devices[] __initdata = {
>>> - &simpad_mq200fb
>>
>> Are you sure this is correct?
>>
>>> + &simpad_keys,
>>> + &simpad_polled_keys,
>>> + &simpad_mq200fb,
>>> + &simpad_i2c,
>>> };
>
> Sorry, I don't see your point here. Could you clarify? Did I miss
> something obvious?
Oh, I'm sorry now. I saw the removal of mq200fb device, but missed the
re-addition of it. So please ignore my comment.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-07-13 12:40 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-07-06 14:42 Jochen Friedrich
2011-07-06 14:42 ` [PATCH 3.1 3/4] ARM:simpad: add GPIO based device definitions 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=4E1D925A.9050601@gmail.com \
--to=dbaryshkov@gmail.com \
--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).