All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@iki.fi>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs
Date: Thu, 3 Dec 2009 08:19:12 +0200	[thread overview]
Message-ID: <20091203061912.GA5626@gw.healthdatacare.com> (raw)
In-Reply-To: <cover.1259674171.git.ext-mika.1.westerberg@nokia.com>

On Tue, Dec 01, 2009 at 03:53:45PM +0200, Mika Westerberg wrote:
>
> This is third version of the series. Purpose of this patch is to allow
> userland to disable GPIO buttons interrupting the CPU. There is now sysfs
> interface that can be used to control the buttons by key code or by switch
> code.
> 
> I merged those previous 2 patches as one. This is because it made little
> sense of having separate patch for adding the 'can_disable' field.
> 
> Changes in v3:
> 	- merged previous 2 patches into one
> 	- buttons have 'can_disable' field instead of irqflags field
> 
> Tested with RX-51.

Hi Dmitry,

Any comments on this? Is it OK to be applied or do I need to change
something.

Thanks again,
MW

  parent reply	other threads:[~2009-12-03  6:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 13:53 [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs Mika Westerberg
2009-12-01 13:53 ` [PATCH v3 1/1] Input: gpio-keys - added support for disabling gpios through sysfs Mika Westerberg
2009-12-03  6:19 ` Mika Westerberg [this message]
2009-12-03  6:26   ` [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs Dmitry Torokhov
2009-12-03  8:09     ` Mika Westerberg
2009-12-15  7:05     ` Mika Westerberg
2009-12-16  8:25       ` Dmitry Torokhov
2010-01-10 11:45         ` Artem Bityutskiy
2010-01-28 21:21         ` Artem Bityutskiy
2010-02-04  8:53           ` Dmitry Torokhov
2010-02-04  9:22             ` Artem Bityutskiy
2010-02-04 18:00             ` Mika Westerberg

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=20091203061912.GA5626@gw.healthdatacare.com \
    --to=mika.westerberg@iki.fi \
    --cc=dmitry.torokhov@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.