linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ben Dooks <ben@simtec.co.uk>
Cc: linux-input@vger.kernel.org
Subject: Re: [patch 0/3] gpio_keys driver updates
Date: Tue, 10 Nov 2009 21:08:55 -0800	[thread overview]
Message-ID: <20091111050855.GA22141@core.coreip.homeip.net> (raw)
In-Reply-To: <20091110225937.922379610@fluff.org.uk>

On Tue, Nov 10, 2009 at 10:59:37PM +0000, Ben Dooks wrote:
> Some updates for the gpio_keys drivers.

Applied all three to 'next', thank you Ben.

-- 
Dmitry

      parent reply	other threads:[~2009-11-11  5:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 22:59 [patch 0/3] gpio_keys driver updates Ben Dooks
2009-11-10 22:59 ` [patch 1/3] gpio_keys: use dev_ macros to report information Ben Dooks
2009-11-10 22:59 ` [patch 2/3] gpio_keys: use <linux/gpio.h> instead of <asm/gpio.h> Ben Dooks
2009-11-10 22:59 ` [patch 3/3] gpio_keys: seperate individual button setup to make code neater Ben Dooks
2009-11-11  5:08 ` 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=20091111050855.GA22141@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=ben@simtec.co.uk \
    --cc=linux-input@vger.kernel.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).