From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: dudl@cypress.com, rubini@cvml.unipv.it,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
olofj@google.com, micahc@google.com,
chromium-os-reviews@chromium.org, vb+kernel@google.com,
msb@chromium.org, olofj@chromium.org
Subject: Re: Add new i2c-based input mouse driver into input subsystem for Cypress trackpad devices. (issue6626009)
Date: Thu, 3 Mar 2011 23:59:22 -0800 [thread overview]
Message-ID: <20110304075921.GA4323@core.coreip.homeip.net> (raw)
In-Reply-To: <bcaec52c66a51e1eda049da36252@google.com>
Hi Dudley,
On Fri, Mar 04, 2011 at 07:49:18AM +0000, dudl@cypress.com wrote:
> Reviewers: rubini_ipvvis.unipv.it, dmitry.torokhov_gmail.com,
> linux-input_vger.kernel.org, linux-kernel_vger.kernel.org, olofj_g,
> Micah C, dudl,
>
> Description:
> Add new i2c-based input mouse driver into input subsystem for
> Cypress trackpad
> devices.
>
> Through this new added driver,
> Cypress i2c-based trackpad devices will be supported in Linux based system
> which are developed based on Cypress self-designed PSOC chipset.
> This driver reads trackpad data using i2c interfaces and report cursor
> moving data and gesture combined keys to input subsystem.
>
>
> Change-Id: I108ad1505f3d34ab24658921a772e937940a1b88
> Signed-off-by: Du, Dudley <dudl@cypress.com>
>
> BUG=None
> TEST=Work fine on ARM tegra2 saeboard and kaen platfrom
>
> Please review this at http://codereview.chromium.org/6626009/
>
Please post your patches in unified diff format on the input mainling
list (linux-input@vger.kernel.org, and please also CC me) - this is
common (and only) way for mainline patch submission.
Thank you.
--
Dmitry
prev parent reply other threads:[~2011-03-04 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 7:49 dudl
2011-03-04 7:59 ` Dmitry Torokhov [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=20110304075921.GA4323@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chromium-os-reviews@chromium.org \
--cc=dudl@cypress.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=micahc@google.com \
--cc=msb@chromium.org \
--cc=olofj@chromium.org \
--cc=olofj@google.com \
--cc=rubini@cvml.unipv.it \
--cc=vb+kernel@google.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
all inboxes | Powered by JetHome®