From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Xianglong Du <Xianglong.Du@csr.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
DL-SHA-WorkGroupLinux <DL-SHA-WorkGroupLinux@internal.csr.com>,
Rongjun Ying <Rongjun.Ying@csr.com>,
Barry Song <Barry.Song@csr.com>
Subject: Re: [PATCH v3] input: sirfsoc-onkey - report onkey untouch event by detecting pin status
Date: Mon, 17 Feb 2014 11:16:58 -0800 [thread overview]
Message-ID: <20140217191658.GA19223@core.coreip.homeip.net> (raw)
In-Reply-To: <CAGsJ_4zjtWV3Z1AJ2bqekXn54rm=k8d4iOi_zzainCEnNGefCw@mail.gmail.com>
On Fri, Feb 14, 2014 at 09:41:06PM +0800, Barry Song wrote:
> >> Input: sirfsoc-onkey - implement open and close methods
> >>
> >> From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> >>
> >> We can control whetehr device generates interrupts or not so let's
> >> implement open and close methods of input device so that we do not do any
> >> processing until there are users.
> >>
> >> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
> Tested-by: Xianglong Du <Xianglong.Du@csr.com>
>
> Dmitry, will you push this one to your tree so that i can rebase others?
I rebased and pushed everything out, please take a look to make sure it
all looks good.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-02-17 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 3:20 [PATCH v3] input: sirfsoc-onkey - report onkey untouch event by detecting pin status Barry Song
2014-02-14 7:57 ` Dmitry Torokhov
2014-02-14 8:49 ` Barry Song
2014-02-14 10:32 ` Xianglong Du
2014-02-14 13:41 ` Barry Song
2014-02-17 19:16 ` Dmitry Torokhov [this message]
2014-02-18 6:11 ` Barry Song
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=20140217191658.GA19223@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=21cnbao@gmail.com \
--cc=Barry.Song@csr.com \
--cc=DL-SHA-WorkGroupLinux@internal.csr.com \
--cc=Rongjun.Ying@csr.com \
--cc=Xianglong.Du@csr.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).