From: Neil Leeder <nleeder@codeaurora.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Horace Fu <horace.fu@quantatw.com>,
Hsin.Wu@quantatw.com, mcuos.com@gmail.com
Subject: Re: [PATCH 0/1] input: keyboard: add qci keyboard driver
Date: Tue, 07 Sep 2010 17:57:59 -0400 [thread overview]
Message-ID: <4C86B567.8030804@codeaurora.org> (raw)
In-Reply-To: <20100903203717.GA6412@core.coreip.homeip.net>
On 9/3/2010 4:37 PM, Dmitry Torokhov wrote:
>
> Does this mean you are not interested in getting drivers for the current
> generation of hardware to mainline?
Hi Dmitry,
That's correct - I don't think there is much future for the current
hardware if we can come up with a cleaner solution for the new versions.
I will test 0xF5 with the new hardware. I think we may still need a
new keyboard driver, just rewritten to have a serio backend. If so, I
will incorporate your changes as well as Trilok's review comments.
Thanks for your reviews and code suggestions.
--
Neil
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-09-07 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 22:14 [PATCH 0/1] input: keyboard: add qci keyboard driver Neil Leeder
2010-08-27 22:18 ` [PATCH 1/1] " Neil Leeder
2010-09-02 8:51 ` Trilok Soni
2010-08-27 22:33 ` [PATCH 0/1] " Dmitry Torokhov
2010-08-30 18:22 ` Neil Leeder
2010-08-30 21:55 ` Dmitry Torokhov
2010-08-31 20:54 ` Neil Leeder
2010-09-01 6:34 ` Dmitry Torokhov
2010-09-03 19:13 ` Neil Leeder
2010-09-03 20:37 ` Dmitry Torokhov
2010-09-07 21:57 ` Neil Leeder [this message]
2010-09-07 22:14 ` Dmitry Torokhov
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=4C86B567.8030804@codeaurora.org \
--to=nleeder@codeaurora.org \
--cc=Hsin.Wu@quantatw.com \
--cc=dmitry.torokhov@gmail.com \
--cc=horace.fu@quantatw.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcuos.com@gmail.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.