From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-input@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [PATCH] input: schedule corgi_ssp and corgi_ts to be removed
Date: Tue, 9 Feb 2010 01:09:19 -0800 [thread overview]
Message-ID: <20100209090918.GA12642@core.coreip.homeip.net> (raw)
In-Reply-To: <f17812d71002081715w485b33bbx3f67afb86c6d8ee1@mail.gmail.com>
On Tue, Feb 09, 2010 at 09:15:38AM +0800, Eric Miao wrote:
> On Tue, Feb 9, 2010 at 2:06 AM, Pavel Machek <pavel@ucw.cz> wrote:
> > On Thu 2010-02-04 16:45:41, Eric Miao wrote:
> >> commit 31cec413e534520111716802833675f53ac99b0b
> >> Author: Eric Miao <eric.y.miao@gmail.com>
> >> Date: Thu Feb 4 16:41:28 2010 -0800
> >>
> >> input: schedule corgi_ssp and corgi_ts to be removed
> >>
> >> Cc: Richard Purdie <rpurdie@rpsys.net>
> >> Signed-off-by: Eric Miao <eric.y.miao@gmail.com>
> >
> > ACK.
> >
>
> Thanks, guys.
>
> Dmitry, I'm hoping these two patches will go through your tree please?
I have it in next, do you want it in .33 instead?
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-09 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 0:45 [PATCH] input: schedule corgi_ssp and corgi_ts to be removed Eric Miao
2010-02-05 7:51 ` Uwe Kleine-König
2010-02-05 10:35 ` Sergei Shtylyov
2010-02-05 11:04 ` Eric Miao
2010-02-05 16:29 ` Richard Purdie
2010-02-08 18:06 ` Pavel Machek
2010-02-09 1:15 ` Eric Miao
2010-02-09 9:09 ` Dmitry Torokhov [this message]
2010-02-09 12:23 ` Eric Miao
2010-02-09 12:33 ` Eric Miao
2010-02-11 7:08 ` Dmitry Torokhov
2010-02-11 7:36 ` Eric Miao
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=20100209090918.GA12642@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
/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).