From: Dan Carpenter <dan.carpenter@oracle.com>
To: Cong Ding <dinggnu@gmail.com>
Cc: Steve Underwood <steveu@coppice.org>,
David Rowe <david@rowetel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jesper Juhl <jj@chaosbits.net>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: echo: remove unused variable
Date: Mon, 10 Dec 2012 12:50:48 +0300 [thread overview]
Message-ID: <20121210095048.GS6568@mwanda> (raw)
In-Reply-To: <20121209151909.GC25293@gmail.com>
On Sun, Dec 09, 2012 at 03:19:09PM +0000, Cong Ding wrote:
> ping!
>
Calm your buns. :P If you don't hear back from anyone, it probably
means that your patch is going to be merged. But you've caught us
at a bad moment because the 3.8 merge window is about to open. It
could take over a month before someone looks at this. Wait for two
weeks after the 3.8-rc1 kernel has been released and then check back
on this.
regards,
dan carpenter
prev parent reply other threads:[~2012-12-10 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 1:21 [PATCH] staging: echo: remove unused variable Cong Ding
2012-12-09 15:19 ` Cong Ding
2012-12-10 9:50 ` Dan Carpenter [this message]
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=20121210095048.GS6568@mwanda \
--to=dan.carpenter@oracle.com \
--cc=david@rowetel.com \
--cc=devel@driverdev.osuosl.org \
--cc=dinggnu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=steveu@coppice.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).