From: Wolfram Sang <wsa@the-dreams.de>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-input@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 2/2] HID: i2c-hid: Do not bind to CHPN0001 touchscreen
Date: Tue, 25 Jul 2017 15:46:58 +0200 [thread overview]
Message-ID: <20170725134658.GB5777@katana> (raw)
In-Reply-To: <alpine.LSU.2.20.1707251457190.4705@cbobk.fhfr.pm>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
> what do we do with this patchset? I think it makes sense for both patches
> to go in via one tree.
Yes.
> Either I can take it through hid.git with your Ack for the first patch, or
> vice versa. Please let me know what you'd prefer.
I'd like use the i2c tree for it. The changes to i2c core are an API
addition while the changes to the HID driver are basically boilerplate.
Makes sense?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-25 13:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 18:55 [PATCH 1/2] i2c: core: Allow the driver to override the default i2c_bus match behavior Hans de Goede
2017-07-22 18:55 ` [PATCH 2/2] HID: i2c-hid: Do not bind to CHPN0001 touchscreen Hans de Goede
2017-07-24 8:19 ` Benjamin Tissoires
2017-07-25 12:58 ` Jiri Kosina
2017-07-25 13:46 ` Wolfram Sang [this message]
2017-07-25 13:58 ` Jiri Kosina
2017-08-17 19:39 ` Wolfram Sang
2017-08-17 22:15 ` Dmitry Torokhov
2017-08-28 13:04 ` Hans de Goede
2017-08-28 16:31 ` Dmitry Torokhov
2017-08-28 16:46 ` Hans de Goede
2017-08-28 12:44 ` Hans de Goede
2017-08-28 12:50 ` Hans de Goede
2017-08-29 8:37 ` Hans de Goede
2017-08-29 8:51 ` Wolfram Sang
2017-08-14 20:13 ` [PATCH 1/2] i2c: core: Allow the driver to override the default i2c_bus match behavior Hans de Goede
2017-08-14 21:21 ` Wolfram Sang
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=20170725134658.GB5777@katana \
--to=wsa@the-dreams.de \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
/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).