From: Artem Bityutskiy <dedekind1@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Mika Westerberg <mika.westerberg@iki.fi>, linux-input@vger.kernel.org
Subject: Re: [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs
Date: Thu, 04 Feb 2010 11:22:59 +0200 [thread overview]
Message-ID: <1265275379.7343.118.camel@localhost> (raw)
In-Reply-To: <20100204085355.GA8003@core.coreip.homeip.net>
On Thu, 2010-02-04 at 00:53 -0800, Dmitry Torokhov wrote:
> Artem, Mika,
>
> I was hoping to do something different about the new 'can_disable' flag
> but unfortunately I don't have enough time and I already sat on the
> patch for way too long. :(
>
> It is applied to my 'next' branch and should get pulled into 2.6.34.
>
> Thank you for your patience and sorry about the delay.
Great, thank you!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-04 9:25 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 ` [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs Mika Westerberg
2009-12-03 6:26 ` 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 [this message]
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=1265275379.7343.118.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mika.westerberg@iki.fi \
/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.