From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>, benjamin.tissoires@redhat.com
Cc: benjamin.tissoires@redhat.com, jikos@kernel.org,
hdegoede@redhat.com, bjorn.andersson@linaro.org,
agross@kernel.org, lee.jones@linaro.org, xnox@ubuntu.com,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 1/5] Input: elan_i2c: Export the device id whitelist
Date: Sat, 22 Jun 2019 23:20:00 -0700 [thread overview]
Message-ID: <20190623062000.GB204275@dtor-ws> (raw)
In-Reply-To: <20190621145042.38637-1-jeffrey.l.hugo@gmail.com>
On Fri, Jun 21, 2019 at 07:50:42AM -0700, Jeffrey Hugo wrote:
> Elan_i2c and hid-quirks work in conjunction to decide which devices each
> driver will handle. Elan_i2c has a whitelist of devices that should be
> consumed by hid-quirks so that there is one master list of devices to
> handoff between the drivers. Put the ids in a header file so that
> hid-quirks can consume it instead of duplicating the list.
>
> Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Benjamin, are you happy with this version?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-06-23 6:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:48 [PATCH v8 0/5] Basic DT support for Lenovo Miix 630 Jeffrey Hugo
2019-06-21 14:50 ` [PATCH v8 1/5] Input: elan_i2c: Export the device id whitelist Jeffrey Hugo
2019-06-23 6:20 ` Dmitry Torokhov [this message]
2019-06-27 14:02 ` Jeffrey Hugo
2019-06-27 14:29 ` Benjamin Tissoires
2019-06-30 7:18 ` Dmitry Torokhov
2019-06-21 14:53 ` [PATCH v8 2/5] HID: quirks: Refactor ELAN 400 and 401 handling Jeffrey Hugo
2019-06-30 7:18 ` Dmitry Torokhov
2019-06-21 14:54 ` [PATCH v8 3/5] arm64: dts: qcom: Add Lenovo Miix 630 Jeffrey Hugo
2019-07-22 23:34 ` Bjorn Andersson
2019-06-21 14:57 ` [PATCH v8 4/5] arm64: dts: qcom: Add HP Envy x2 Jeffrey Hugo
2019-06-21 14:59 ` [PATCH v8 5/5] arm64: dts: qcom: Add Asus NovaGo TP370QL Jeffrey Hugo
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=20190623062000.GB204275@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=agross@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=jeffrey.l.hugo@gmail.com \
--cc=jikos@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=xnox@ubuntu.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).