From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Vishnu Sankar <vishnuocv@gmail.com>
Cc: Mark Pearson <mpearson-lenovo@squebb.ca>,
dmitry.torokhov@gmail.com, hmh@hmh.eng.br,
Hans de Goede <hansg@kernel.org>,
corbet@lwn.net, derekjohn.clark@gmail.com,
linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
ibm-acpi-devel@lists.sourceforge.net, linux-doc@vger.kernel.org,
platform-driver-x86@vger.kernel.org, vsankar@lenovo.com
Subject: Re: [PATCH v7 3/3] Documentation: thinkpad-acpi - Document doubletap_enable attribute
Date: Mon, 9 Mar 2026 10:03:53 +0200 (EET) [thread overview]
Message-ID: <991f8a08-7c5d-5611-7904-6c5d336a74a3@linux.intel.com> (raw)
In-Reply-To: <20260209063355.491189-4-vishnuocv@gmail.com>
On Mon, 9 Feb 2026, Vishnu Sankar wrote:
> Document the doubletap_enable sysfs attribute for ThinkPad ACPI driver.
>
> Signed-off-by: Vishnu Sankar <vishnuocv@gmail.com>
> ---
> + * 1 - doubletap events are processed (default)
> + * 0 - doubletap events are filtered out (ignored)
There's something odd in space vs tab here.
--
i.
next prev parent reply other threads:[~2026-03-09 8:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 6:33 [PATCH v7 0/3] TrackPoint doubletap enablement and user control Vishnu Sankar
2026-02-09 6:33 ` [PATCH v7 1/3] input: trackpoint - Enable doubletap by default on capable devices Vishnu Sankar
2026-03-09 8:01 ` Ilpo Järvinen
2026-03-10 2:11 ` Vishnu Sankar
2026-03-10 9:15 ` Ilpo Järvinen
2026-03-10 9:21 ` Vishnu Sankar
2026-03-10 9:30 ` Ilpo Järvinen
2026-03-10 11:54 ` Vishnu Sankar
2026-02-09 6:33 ` [PATCH v7 2/3] platform/x86: thinkpad_acpi: Add sysfs control for TrackPoint double-tap Vishnu Sankar
2026-02-09 6:33 ` [PATCH v7 3/3] Documentation: thinkpad-acpi - Document doubletap_enable attribute Vishnu Sankar
2026-03-09 8:03 ` Ilpo Järvinen [this message]
2026-03-10 1:37 ` Vishnu Sankar
2026-02-23 23:28 ` [PATCH v7 0/3] TrackPoint doubletap enablement and user control Vishnu Sankar
2026-03-06 13:51 ` Mark Pearson
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=991f8a08-7c5d-5611-7904-6c5d336a74a3@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=corbet@lwn.net \
--cc=derekjohn.clark@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hansg@kernel.org \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vishnuocv@gmail.com \
--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