From: Shawn Guo <shawn.guo@freescale.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Shawn Guo <shawn.guo@linaro.org>,
patches@linaro.org, devicetree-discuss@lists.ozlabs.org,
Phil Blundell <pb@handhelds.org>,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] Input: gpio-keys: add device tree probe support
Date: Tue, 19 Jul 2011 09:22:52 +0800 [thread overview]
Message-ID: <20110719012251.GC3838@S2100-06.ap.freescale.net> (raw)
In-Reply-To: <201107181005.52725.dmitry.torokhov@gmail.com>
On Mon, Jul 18, 2011 at 10:05:52AM -0700, Dmitry Torokhov wrote:
> Hi Shawn,
>
> On Monday, July 18, 2011 09:45:08 AM Shawn Guo wrote:
> > It adds device tree probe support for gpio-keys driver.
>
> There is already a patch by David Jander adding device tree support to
> the driver; I intend to apply it.
>
Sorry, I was not aware of David's patch. No problem, you can pick
whichever you want. All I want to see is gpio_keys gets device tree
support, because I need to convert several board files to device tree
and the gpio_keys seems to be the only one missing device tree support
there.
--
Regards,
Shawn
next prev parent reply other threads:[~2011-07-19 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 16:45 [PATCH 0/2] add device tree probe support for gpio_keys Shawn Guo
2011-07-18 16:45 ` [PATCH 1/2] Input: gpio-keys: do not reference platform_data after .probe exits Shawn Guo
2011-07-18 17:02 ` Dmitry Torokhov
2011-07-18 17:15 ` Grant Likely
2011-07-18 17:24 ` Dmitry Torokhov
2011-07-19 1:17 ` Shawn Guo
[not found] ` <20110719011725.GB3838-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2011-07-19 7:48 ` Russell King - ARM Linux
2011-07-19 8:56 ` Shawn Guo
2011-07-18 16:45 ` [PATCH 2/2] Input: gpio-keys: add device tree probe support Shawn Guo
2011-07-18 17:05 ` Dmitry Torokhov
2011-07-19 1:22 ` Shawn Guo [this message]
2011-07-19 3:55 ` Shawn Guo
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=20110719012251.GC3838@S2100-06.ap.freescale.net \
--to=shawn.guo@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=patches@linaro.org \
--cc=pb@handhelds.org \
--cc=shawn.guo@linaro.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).