From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Philipp Zabel <philipp.zabel@gmail.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
Paul Sokolovsky <pmiscml@gmail.com>
Subject: Re: [PATCH] gpio-keys
Date: Thu, 15 Feb 2007 15:03:16 -0500 [thread overview]
Message-ID: <d120d5000702151203g72016ec0n8dd25896e482c847@mail.gmail.com> (raw)
In-Reply-To: <1171537620.27151.5.camel@localhost.localdomain>
On 2/15/07, Philipp Zabel <philipp.zabel@gmail.com> wrote:
> Now that the common GPIO API is in mainline, gpio-keys should use it.
> This adds support for at least SA1100 and S3C24xx CPUs.
>
> Signed-off-by: Philipp Zabel <philipp.zabel@gmail.com>
>
Will apply, thank you Philipp.
--
Dmitry
prev parent reply other threads:[~2007-02-15 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 11:06 [PATCH] gpio-keys Philipp Zabel
2007-02-15 12:19 ` Philipp Zabel
2007-02-15 20:03 ` Dmitry Torokhov [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=d120d5000702151203g72016ec0n8dd25896e482c847@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=philipp.zabel@gmail.com \
--cc=pmiscml@gmail.com \
/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).