From: Greg KH <gregkh@linuxfoundation.org>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: omar.ramirez@ti.com, vjaquez@igalia.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH NEXT v2]staging: tidspbridge: Fix typos.
Date: Mon, 30 Jul 2012 07:52:52 -0700 [thread overview]
Message-ID: <20120730145252.GA24883@kroah.com> (raw)
In-Reply-To: <501699CA.1050808@gmail.com>
On Mon, Jul 30, 2012 at 07:27:22AM -0700, Justin P. Mattock wrote:
> greg!
> I know how things can get lost in the sands of time, so when you get
> a chance is this patch good? or do I need to resend?
It's the middle of the merge window, when I can't do anything that is
for 3.7, sorry. Please wait until after 3.6-rc1 is out, and then I will
start working on my backlog of patches.
greg k-h
next prev parent reply other threads:[~2012-07-30 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 3:40 [PATCH NEXT v2]staging: tidspbridge: Fix typos Justin P. Mattock
2012-07-30 14:27 ` Justin P. Mattock
2012-07-30 14:52 ` Greg KH [this message]
2012-07-30 15:22 ` Dan Carpenter
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=20120730145252.GA24883@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--cc=vjaquez@igalia.com \
/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