From: Pavel Machek <pavel@ucw.cz>
To: Hemanth V <hemanthv@ti.com>, kernel list <linux-kernel@vger.kernel.org>
Cc: linux-input@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: Merge plans for Staging Synaptics Touchscreen Driver
Date: Mon, 29 Mar 2010 15:12:40 +0200 [thread overview]
Message-ID: <20100329131136.GA26586@ucw.cz> (raw)
In-Reply-To: <49670.10.24.255.17.1269864940.squirrel@dbdmail.itg.ti.com>
Hi!
> >>> Pl add (if required) below tested by for the staging driver.
> >
> >>
> >> 1) are you able to use driver in staging?
> >
> > Yes I am able to use staging driver for single
> > touch events.
Good.
> >> at minimum, non-standard multitouch support needs to be removed before
> >> merging to input. Do you have time to help?
> >
> > Could you review the below patch.
>
> Forgot to remove unused variables in earlier patch, here's
> the updated one.
Thanks, seems ok.
> Remove non-standard multi touch support.
>
> Signed-off-by: Hemanth V <hemanthv@ti.com>
ACK.
Now... you probably want to send the patch to Greg. And then, I guess
you could take the patch from staging, and ask for another round of
review on linux-input.
If you could figure out if threaded interrupts can be used for this
driver, that would be welcome bonus.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-03-29 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:28 Merge plans for Staging Synaptics Touchscreen Driver Hemanth V
2010-03-23 14:00 ` Aguirre, Sergio
2010-03-23 14:42 ` Hemanth V
2010-03-26 14:44 ` Pavel Machek
2010-03-29 11:55 ` Hemanth V
[not found] ` <33474.10.24.255.18.1269863733.squirrel@dbdmail.itg.ti.com>
2010-03-29 12:15 ` Hemanth V
2010-03-29 13:12 ` Pavel Machek [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=20100329131136.GA26586@ucw.cz \
--to=pavel@ucw.cz \
--cc=hemanthv@ti.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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