The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Jingle Wu 吳金國" <jingle.wu@emc.com.tw>
Cc: "Yao Yuan" <yaoyuan0329os@gmail.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Vishnu Sankar" <vishnuocv@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Phoenix Huang 黃世鵬" <phoenix@emc.com.tw>,
	"Stanley Chen 陳建維" <stanley.chen@emc.com.tw>
Subject: Re: [PATCH 1/1] Input: trackpoint - Add new ELAN trackpoint device variant id 7
Date: Wed, 11 Nov 2026 21:33:05 -0800	[thread overview]
Message-ID: <avVPRySmoH_KKHa6@google.com> (raw)
In-Reply-To: <TY0PR0101MB47865DFC765932B9E6C3E1C0DC702@TY0PR0101MB4786.apcprd01.prod.exchangelabs.com>

Hi Jingle,

On Thu, Nov 12, 2026 at 05:26:46AM +0000, Jingle Wu 吳金國 wrote:
> Hi Yao:
> 
> Upon inquiry, it was confirmed that a black TrackPoint stick (0x07)
> underneath the red TrackPoint cap corresponds to a vendor that is
> compatible with the Windows ELAN driver.

Are you at liberty to share the vendor name? Or should we mark it as
"Elan" or "Elan-compatible"?

Thanks.

-- 
Dmitry

  reply	other threads:[~2026-11-12  5:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 13:08 [PATCH 0/1] Input/trackpoint: Add new ELAN trackpoint device variant id 7 Yuan Yao
2026-11-02 13:08 ` [PATCH 1/1] Input: trackpoint - " Yuan Yao
2026-11-10  2:36   ` Dmitry Torokhov
2026-11-10  5:26     ` Jingle Wu 吳金國
2026-11-10 13:48       ` Yao Yuan
2026-11-11  5:26         ` Jingle Wu 吳金國
2026-11-11 14:04           ` Yao Yuan
2026-11-12  5:26             ` Jingle Wu 吳金國
2026-11-12  5:33               ` Dmitry Torokhov [this message]
2026-11-12  7:14                 ` Vishnu Sankar
2026-11-12  8:43                   ` Vishnu Sankar
2026-11-12 12:45                   ` Yao Yuan
2026-11-12 12:36               ` Yao Yuan
2026-11-12 12:49               ` Yao Yuan
2026-11-10 13:22     ` Yao Yuan

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=avVPRySmoH_KKHa6@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jingle.wu@emc.com.tw \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phoenix@emc.com.tw \
    --cc=stanley.chen@emc.com.tw \
    --cc=vishnuocv@gmail.com \
    --cc=yaoyuan0329os@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