From: Andrew Duggan <aduggan@synaptics.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Vincent Huang <vincent.huang@tw.synaptics.com>,
Nick Dyer <nick.dyer@itdev.co.uk>
Subject: Re: [PATCH v2] HID: rmi: Make hid-rmi a transport driver for synaptics-rmi4
Date: Wed, 15 Jun 2016 17:05:41 -0700 [thread overview]
Message-ID: <5761ED55.4090502@synaptics.com> (raw)
In-Reply-To: <20160615094137.GY24234@mail.corp.redhat.com>
On 06/15/2016 02:41 AM, Benjamin Tissoires wrote:
> On Jun 15 2016 or thereabouts, Jiri Kosina wrote:
>> On Fri, 3 Jun 2016, Andrew Duggan wrote:
>>
>>> The Synaptics RMI4 driver provides support for RMI4 devices. Instead of
>>> duplicating the RMI4 processing code, make hid-rmi a transport driver
>>> and register it with the Synaptics RMI4 core.
>>>
>>> Signed-off-by: Andrew Duggan <aduggan@synaptics.com>
>> Is there any update on the Input series please?
> FWIW, I just reviewed it. Now the ball is in Dmitry's hand (I don't
> think it needs a resubmission).
Linus had some suggestions regarding the naming of the device tree
properties in patch 3. I can either resubmit the series with those
changes plus what Benjamin identified. Or I can resubmit the patch 3 as
a standalone patch later so that the rest of the series can be applied.
I'll do which ever option is less of a burden on the reviewers.
Andrew
> Cheers,
> Benjamin
>
>> Thanks,
>>
>> --
>> Jiri Kosina
>> SUSE Labs
>>
next prev parent reply other threads:[~2016-06-16 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 18:41 [PATCH v2] HID: rmi: Make hid-rmi a transport driver for synaptics-rmi4 Andrew Duggan
2016-06-03 20:11 ` kbuild test robot
2016-06-06 9:25 ` Jiri Kosina
2016-06-15 7:23 ` Jiri Kosina
2016-06-15 9:41 ` Benjamin Tissoires
2016-06-16 0:05 ` Andrew Duggan [this message]
2016-06-15 9:54 ` Benjamin Tissoires
2016-06-15 23:51 ` Andrew Duggan
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=5761ED55.4090502@synaptics.com \
--to=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.dyer@itdev.co.uk \
--cc=vincent.huang@tw.synaptics.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).