From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: "Peter Hutterer" <peter.hutterer@redhat.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Henrique de Moraes Holschuh" <hmh@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Nitin Joshi1" <njoshi1@lenovo.com>,
"Vishnu Sankar" <vsankar@lenovo.com>
Subject: Re: [PATCH 1/4] Input: Add trackpoint doubletap and system debug info keycodes
Date: Mon, 15 Apr 2024 12:40:36 -0700 [thread overview]
Message-ID: <Zh2CtKy1NfKfojzS@google.com> (raw)
In-Reply-To: <91593303-4a6a-49c9-87a0-bb6f72f512a1@app.fastmail.com>
On Wed, Apr 10, 2024 at 10:48:10PM -0400, Mark Pearson wrote:
>
> I have a stronger preference to keep the KEY_DOUBLECLICK - that one seems less controversial as a genuine new input event.
Please see my response to Peter's letter. I think it very much depends
on how it will be used (associated with the pointer or standalone as it
is now).
For standalone application, recalling your statement that on Win you
have this gesture invoke configuration utility I would argue for
KEY_CONFIG for it.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-04-15 19:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 21:07 [PATCH 0/4] platform/x86,input: Support for new events on Mark Pearson
2024-03-24 21:07 ` [PATCH 1/4] Input: Add trackpoint doubletap and system debug info keycodes Mark Pearson
2024-04-08 12:45 ` Hans de Goede
2024-04-08 23:31 ` Dmitry Torokhov
2024-04-09 0:00 ` Mark Pearson
2024-04-09 10:16 ` Hans de Goede
2024-04-09 21:54 ` Dmitry Torokhov
2024-04-09 5:23 ` Peter Hutterer
2024-04-09 21:47 ` Dmitry Torokhov
2024-04-10 1:20 ` Dmitry Torokhov
2024-04-10 2:17 ` Mark Pearson
2024-04-11 0:02 ` Dmitry Torokhov
2024-04-11 2:48 ` Mark Pearson
2024-04-15 19:40 ` Dmitry Torokhov [this message]
2024-04-15 19:50 ` Hans de Goede
2024-04-15 19:58 ` Dmitry Torokhov
2024-04-15 20:28 ` Mark Pearson
2024-04-15 22:54 ` Dmitry Torokhov
2024-04-15 23:57 ` Mark Pearson
2024-04-16 8:33 ` Hans de Goede
2024-04-16 12:48 ` Mark Pearson
2024-04-16 13:03 ` Hans de Goede
2024-04-16 8:35 ` Hans de Goede
2024-04-11 12:30 ` Hans de Goede
2024-04-15 19:35 ` Dmitry Torokhov
2024-04-15 19:47 ` Hans de Goede
2024-04-15 19:55 ` Dmitry Torokhov
2024-04-10 4:32 ` Peter Hutterer
2024-04-15 19:32 ` Dmitry Torokhov
2024-03-24 21:07 ` [PATCH 2/4] platform/x86: thinkpad_acpi: Support for trackpoint doubletap Mark Pearson
2024-04-08 13:04 ` Hans de Goede
2024-04-08 14:56 ` [ibm-acpi-devel] " Mark Pearson
2024-03-24 21:08 ` [PATCH 3/4] platform/x86: thinkpad_acpi: Support for system debug info hotkey Mark Pearson
2024-04-08 13:11 ` Hans de Goede
2024-04-08 14:56 ` Mark Pearson
2024-03-24 21:08 ` [PATCH 4/4] platform/x86: thinkpad_acpi: Support hotkey to disable trackpoint doubletap Mark Pearson
2024-04-08 13:13 ` Hans de Goede
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=Zh2CtKy1NfKfojzS@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=njoshi1@lenovo.com \
--cc=peter.hutterer@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vsankar@lenovo.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).