From: Stephen Warren <swarren@wwwdotorg.org>
To: Benson Leung <bleung@chromium.org>, Nick Dyer <nick.dyer@itdev.co.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Yufeng Shen <miletus@chromium.org>,
Daniel Kurtz <djkurtz@chromium.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra
Date: Tue, 06 May 2014 16:35:12 -0600 [thread overview]
Message-ID: <536963A0.4060506@wwwdotorg.org> (raw)
In-Reply-To: <CANLzEkv8To0gWWYBF3JjRDqt+1xGUhQiYJJUwovVhBDEMW569Q@mail.gmail.com>
On 05/06/2014 04:16 PM, Benson Leung wrote:
> Hi Stephen,
>
> On Tue, May 6, 2014 at 3:13 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> This series contains the minimum number of patches required to make the
>> Atmel MXT touchpad work on NVIDIA Tegra, which requires the device to be
>> instantiated from device tree rather than from a C board file.
>>
>> These patches are based on patches in the ChromeOS kernel. However, I took
>> a different approach to the devicetree-doesn't-provide-platform-data issue.
>> Rather than amending all users of platform data to work with or without it,
>> as the patches in the ChromeOS kernel do, I implemented a single function
>> mxt_parse_dt() to create a platform data structure from DT. This isolates
>> the changes required to a single function, rather than spreading them all
>> over the driver.
>
> Please coordinate with Nick Dyer, who has a long patch series that's
> been approved but not yet merged into the input tree. The few patches
> you've picked from the Chrome OS kernel overlap with his patch series.
Ah I remember you mentioning that before. Is Nick's work still active?
The link you sent me to the "latest status" was nearly a year ago:
https://lkml.org/lkml/2013/6/27/311
... and while the github link you sent:
https://github.com/ndyer/linux/commits/for-next-20140316-v8
... has much more recent activity, it hasn't been touched /that/
recently either.
To be honest, it'd be a bit off-putting to hold up a trivial patch
series like this and make it wait for a huge refactoring series that's
obviously been dragging on for a long time...
next prev parent reply other threads:[~2014-05-06 22:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:13 [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra Stephen Warren
2014-05-06 22:13 ` [PATCH 1/4] Input: atmel_mxt_ts - Set pointer emulation if is_tp Stephen Warren
2014-05-06 22:13 ` [PATCH 2/4] Input: atmel_mxt_ts - Read resolution from device memory Stephen Warren
2014-05-06 22:13 ` [PATCH 3/4] Input: atmel_mxt_ts: define a device tree binding Stephen Warren
2014-05-06 22:13 ` [PATCH 4/4] Input: atmel_mxt_ts: implement device tree parsing Stephen Warren
2014-05-06 22:16 ` [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra Benson Leung
2014-05-06 22:35 ` Stephen Warren [this message]
2014-05-08 16:01 ` Nick Dyer
2014-05-08 16:41 ` Stephen Warren
2014-05-08 17:26 ` Dmitry Torokhov
2014-05-08 19:56 ` Nick Dyer
2014-05-09 18:49 ` Mark Brown
2014-05-13 1:17 ` Dmitry Torokhov
2014-05-08 19:50 ` Nick Dyer
2014-05-12 20:02 ` Stephen Warren
2014-05-13 1:16 ` Dmitry Torokhov
2014-05-13 2:31 ` Stephen Warren
2014-05-16 16:21 ` Nick Dyer
2014-05-16 16:40 ` Stephen Warren
2014-05-20 16:19 ` Nick Dyer
2014-06-11 18:17 ` Stephen Warren
2014-06-12 11:25 ` Nick Dyer
2014-06-12 17:12 ` Stephen Warren
2014-06-12 17:37 ` Stephen Warren
2014-06-30 16:11 ` Stephen Warren
2014-06-02 9:50 ` Sekhar Nori
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=536963A0.4060506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bleung@chromium.org \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=miletus@chromium.org \
--cc=nick.dyer@itdev.co.uk \
--cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.