From: Pavel Machek <pavel@ucw.cz>
To: Rakesh Iyer <riyer@nvidia.com>
Cc: "tsoni@codeaurora.org" <tsoni@codeaurora.org>,
"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"shubhrajyoti@ti.com" <shubhrajyoti@ti.com>,
"ccross@android.com" <ccross@android.com>,
"konkers@android.com" <konkers@android.com>,
"olof@lixom.net" <olof@lixom.net>, Andrew Chew <AChew@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH 1/1] input: tegra-kbc - Add tegra keyboard driver
Date: Wed, 12 Jan 2011 23:02:55 +0100 [thread overview]
Message-ID: <20110112220254.GA4214@elf.ucw.cz> (raw)
In-Reply-To: <1FC56210173BB445BD77F608D6FB8D03165A00806D@HQMAIL03.nvidia.com>
On Wed 2011-01-12 13:59:45, Rakesh Iyer wrote:
> Hi all.
>
> I apologize for not specifying the PATCH indicator as "PATCH v4".
>
> Sorry for the inconvenience caused.
Well, that is not huge problem, but short note of changes from last
version would be welcome.
AFAICT, FN handling was reworked...?
> > + KEY_F10, KEY_F9, KEY_BACKSPACE, KEY_3,
> > + KEY_2, KEY_UP, KEY_PRINT, KEY_PAUSE,
But now I'm confused; does hardware have Fx keys (F10 above) or not?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2011-01-12 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 21:52 riyer
2011-01-12 21:59 ` Rakesh Iyer
2011-01-12 22:02 ` Pavel Machek [this message]
2011-01-12 22:13 ` Rakesh Iyer
2011-01-12 22:26 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2011-01-05 1:03 riyer
2011-01-05 6:01 ` Shubhrajyoti
2011-01-05 8:36 ` Trilok Soni
2011-01-05 22:02 ` Rakesh Iyer
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=20110112220254.GA4214@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=AChew@nvidia.com \
--cc=ccross@android.com \
--cc=dmitry.torokhov@gmail.com \
--cc=konkers@android.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=riyer@nvidia.com \
--cc=shubhrajyoti@ti.com \
--cc=tsoni@codeaurora.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®