From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: michael.hennerich@analog.com
Cc: akpm@linux-foundation.org, linux-input@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org, drivers@analog.com
Subject: Re: [PATCH] input: keyboard: adp5588-keys: unify common header defines
Date: Tue, 2 Nov 2010 06:04:35 -0700 [thread overview]
Message-ID: <20101102130434.GA11778@core.coreip.homeip.net> (raw)
In-Reply-To: <1288701072-336-1-git-send-email-michael.hennerich@analog.com>
On Tue, Nov 02, 2010 at 01:31:12PM +0100, michael.hennerich@analog.com wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> No functional changes.
> Unify adp5588-gpio and adp5588-keys common header defines.
> (as per Andrew Morton request)
> For consistency move remaining defines and prefix accordingly.
>
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Applied, thanks Michael.
--
Dmitry
prev parent reply other threads:[~2010-11-02 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 12:31 [PATCH] input: keyboard: adp5588-keys: unify common header defines michael.hennerich
2010-11-02 13:04 ` 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=20101102130434.GA11778@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=drivers@analog.com \
--cc=linux-input@vger.kernel.org \
--cc=michael.hennerich@analog.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).