From: Dmitry Torokhov <dtor@insightbb.com>
To: Karl Pickett <karl.pickett@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-input@atrey.karlin.mff.cuni.cz,
Vincent Vanackere <vincent.vanackere@gmail.com>
Subject: Re: [PATCH] Make ati_remote button repeat sensitivity soft-configurable (V2)
Date: Tue, 10 Apr 2007 01:03:05 -0400 [thread overview]
Message-ID: <200704100103.06854.dtor@insightbb.com> (raw)
In-Reply-To: <f9be06770704050723p1a01f9adyae8fc671c91edb7c@mail.gmail.com>
On Thursday 05 April 2007 10:23, Karl Pickett wrote:
> Dmitry, please use this instead of my previous patch. Thanks to
> Vincent for the code review , fixes, and testing.
>
Applied to the input tree; thank you Karl and Vincent.
--
Dmitry
prev parent reply other threads:[~2007-04-10 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 14:23 [PATCH] Make ati_remote button repeat sensitivity soft-configurable (V2) Karl Pickett
2007-04-10 5: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=200704100103.06854.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=karl.pickett@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vincent.vanackere@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).