public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	vjaquez@igalia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH NEXT v2]staging: tidspbridge: Fix typos.
Date: Mon, 30 Jul 2012 18:22:29 +0300	[thread overview]
Message-ID: <20120730152229.GH4352@mwanda> (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?
> 

The merge window is still open.  No one is looking at patches until
-rc1 is released.

regards,
dan carpenter


      parent reply	other threads:[~2012-07-30 15:23 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
2012-07-30 15:22   ` 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=20120730152229.GH4352@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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