From: 'Dmitry Torokhov' <dmitry.torokhov@gmail.com>
To: "Dave.Wang" <dave.wang@emc.com.tw>
Cc: Linux-kernel@vger.kernel.org, Linux-input@vger.kernel.org,
jingle.wu@emc.com.tw,
'Benjamin Tissoires' <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] Input: elan_i2c - Add more hardware ID for Lenovo laptop
Date: Wed, 8 Jul 2020 22:30:46 -0700 [thread overview]
Message-ID: <20200709053046.GH3273837@dtor-ws> (raw)
In-Reply-To: <000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw>
On Mon, Dec 02, 2019 at 11:07:26AM +0800, Dave.Wang wrote:
> Hi Dmitry,
>
> List device with its corresponding hardware ID as below patch,
> Please check , thanks!
>
> Add more hardware ID for Lenovo laptop.
>
> Signed-off-by: Dave Wang <dave.wang@emc.com.tw>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2020-07-09 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 8:12 [PATCH] Input: elan_i2c - Add more hardware ID for Lenovo laptop Dave.Wang
2019-12-02 1:02 ` Dmitry Torokhov
2019-12-02 3:07 ` Dave.Wang
2020-07-09 5:30 ` '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=20200709053046.GH3273837@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Linux-input@vger.kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=dave.wang@emc.com.tw \
--cc=jingle.wu@emc.com.tw \
/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).