From: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>, Lee Jones <lee.jones@linaro.org>,
xnox@ubuntu.com, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 1/5] Input: elan_i2c: Export the device id whitelist
Date: Fri, 21 Jun 2019 08:34:26 -0600 [thread overview]
Message-ID: <CAOCk7NoKB6UtA3g-0+Yxi4Y46PDqapnOH0dHH0CupvnQ=ZSKVQ@mail.gmail.com> (raw)
In-Reply-To: <CAKdAkRRstvEWXtwnLCMKoW6PcCz0W3+M9iYqVFshJpw6y_=9bA@mail.gmail.com>
On Thu, Jun 20, 2019 at 10:34 PM Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
>
> Hi Jeffrey,
>
> On Thu, Jun 20, 2019 at 7:33 AM Jeffrey Hugo <jeffrey.l.hugo@gmail.com> wrote:
> > #ifdef CONFIG_OF
> > -static const struct of_device_id elan_of_match[] = {
> > - { .compatible = "elan,ekth3000" },
> > - { /* sentinel */ }
> > -};
>
> I think OF IDs should stay in this file since we agreed HID will not
> be checking them.
I thought it would be convenient to keep all the IDs in one place, but
I'll put these back.
>
> > MODULE_DEVICE_TABLE(of, elan_of_match);
> > #endif
> >
> > diff --git a/include/linux/input/elan-i2c-ids.h b/include/linux/input/elan-i2c-ids.h
> > new file mode 100644
> > index 000000000000..8130bbebbdda
> > --- /dev/null
> > +++ b/include/linux/input/elan-i2c-ids.h
> > @@ -0,0 +1,68 @@
> > +/* SPDX-License-Identifier: GPL-2.0 */
> > +/*
> > + * Elan I2C Touchpad devide whitelist
>
> s/devide/device/
Doh. Will fix.
>
> > + *
> > + * Copyright (C) 2019 Jeffrey Hugo. All rights reserved.
>
> This just moves the code around. If anything I'd say it should keep
> the original Elan copyright.
Ok. No problem.
>
> Thanks.
>
> --
> Dmitry
next prev parent reply other threads:[~2019-06-21 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 14:28 [PATCH v7 0/5] Basic DT support for Lenovo Miix 630 Jeffrey Hugo
2019-06-20 14:33 ` [PATCH v7 1/5] Input: elan_i2c: Export the device id whitelist Jeffrey Hugo
2019-06-21 4:34 ` Dmitry Torokhov
2019-06-21 14:34 ` Jeffrey Hugo [this message]
2019-06-20 14:35 ` [PATCH v7 2/5] HID: quirks: Refactor ELAN 400 and 401 handling Jeffrey Hugo
2019-06-20 14:37 ` [PATCH v7 3/5] arm64: dts: qcom: Add Lenovo Miix 630 Jeffrey Hugo
2019-06-20 14:38 ` [PATCH v7 4/5] arm64: dts: qcom: Add HP Envy x2 Jeffrey Hugo
2019-06-20 14:39 ` [PATCH v7 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='CAOCk7NoKB6UtA3g-0+Yxi4Y46PDqapnOH0dHH0CupvnQ=ZSKVQ@mail.gmail.com' \
--to=jeffrey.l.hugo@gmail.com \
--cc=agross@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.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).