From: Christopher Heiny <Cheiny@synaptics.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Balint Czobor <czoborbalint@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/1] drivers: input: touchscreen: Initial support for SYNAPTICS_I2C_RMI touchscreen
Date: Tue, 9 Jul 2013 00:09:38 +0000 [thread overview]
Message-ID: <BFABBC009FBA1C43B207B15FD485ABD92FDEC0F2@usw-mail3.synaptics-inc.local> (raw)
In-Reply-To: <3502283.ihV8RhfYF2@dtor-d630.eng.vmware.com>
Sorry if this is a duplicate - there's some email issues here at work.
On 07/08/2013 03:39 PM, Dmitry Torokhov wrote:
> On Monday, July 08, 2013 10:21:16 PM Christopher Heiny wrote:
>> On 07/08/2013 01:25 AM, Balint Czobor wrote:
>>> Add initial support for Synaptics RMI over I2C based touchscreens.
>>
>> This is pretty old code - it looks like a modification of patches we
>> submitted last year. Is there some reason you're not basing it off the
>> latest checkins in synaptics-rmi4 branch of Dmitry's input tree?
>
> That branch is fairly old as well, I believe you have much never
> version on Github?
Yes, I do, but I figured your branch was the reference.
Balint - there newest code is here:
https://github.com/mightybigcar/synaptics-rmi4
There are two branches. The main branch tracks work intended for the
next submission. The development branch is a superset of that work,
including all currently supported and in development RMI4 function
implementations.
If you would like to integrate that work into your kernel, I'll be happy
to help out with that (and I suspect Dmitry and others would be too).
Thanks,
Chris
prev parent reply other threads:[~2013-07-09 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 8:25 Balint Czobor
[not found] ` <51DB3B13.7070805@synaptics.com>
2013-07-08 22:21 ` Christopher Heiny
2013-07-08 22:39 ` Dmitry Torokhov
2013-07-09 0:09 ` Christopher Heiny [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=BFABBC009FBA1C43B207B15FD485ABD92FDEC0F2@usw-mail3.synaptics-inc.local \
--to=cheiny@synaptics.com \
--cc=czoborbalint@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®