From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: riyer@nvidia.com
Cc: rydberg@euromail.se, amartin@nvidia.com, olof@lixom.net,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [v1] Input: tegra-kbc - modify keypress wakeup logic.
Date: Mon, 2 May 2011 17:48:54 -0700 [thread overview]
Message-ID: <BANLkTimFKzQk0u3Kwq0MXRXEjUg8xb1JOA@mail.gmail.com> (raw)
In-Reply-To: <1304382188-29530-1-git-send-email-riyer@nvidia.com>
Hi Rakesh,
On Mon, May 2, 2011 at 5:23 PM, <riyer@nvidia.com> wrote:
> From: Rakesh Iyer <riyer@nvidia.com>
>
> Modify wakeup logic so either all keypresses wake the system or none do.
You need to provide justification for this change (i.e. why the new
way is better).
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-05-03 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 0:23 [v1] Input: tegra-kbc - modify keypress wakeup logic riyer
2011-05-03 0:48 ` Dmitry Torokhov [this message]
2011-05-03 17:02 ` Rakesh Iyer
2011-05-07 5:56 ` 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=BANLkTimFKzQk0u3Kwq0MXRXEjUg8xb1JOA@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=amartin@nvidia.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=riyer@nvidia.com \
--cc=rydberg@euromail.se \
/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;
as well as URLs for NNTP newsgroup(s).