From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5]NEXT:drivers:staging:nvec:nvec.h Fix typos in staging:nvec
Date: Mon, 26 Mar 2012 08:00:56 -0700 [thread overview]
Message-ID: <4F7084A8.10308@gmail.com> (raw)
In-Reply-To: <20120326144830.GA22373@kroah.com>
On 03/26/2012 07:48 AM, Greg KH wrote:
> On Mon, Mar 26, 2012 at 07:29:27AM -0700, Justin P. Mattock wrote:
>> before these get lost in the sands of time; are you wanting to pick
>> these up?
>
> You sent these during the merge window, so I have to wait until after
> 3.4-rc1 is out before I can accept them. Don't worry, they are in my
> to-apply queue and I will get to them eventually, they are not lost.
>
> patience,
>
> greg k-h
>
ahh.. then in the future I will hold on sending anything until *rc1 is
out. glad they are not lost.. patch management is a good thing!
patience as well..
cheers!
Justin P. Mattock
next prev parent reply other threads:[~2012-03-26 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 15:17 [PATCH 1/5]NEXT:drivers:staging:nvec:nvec.h Fix typos in staging:nvec Justin P. Mattock
2012-03-19 15:17 ` [PATCH 2/5]NEXT:drivers:staging:ozwpan:ozhcd.c Fix typos in staging:ozwpan Justin P. Mattock
2012-03-19 15:27 ` Chris Kelly
2012-03-19 15:17 ` [PATCH 3/5]NEXT:drivers:staging:olpc_dcon:olpc_dcon_xo_1.c Fix typo in staging:olpc_dcon Justin P. Mattock
2012-03-19 15:17 ` [PATCH 4/5]NEXT:drivers:staging:panel:panel.c Fix typo in staging:panel Justin P. Mattock
2012-03-19 15:17 ` [PATCH 5/5]NEXT:drivers:staging:quatech_usb2:quatech_usb2.c Fix typo in staging:quatech_usb2 Justin P. Mattock
2012-03-26 14:29 ` [PATCH 1/5]NEXT:drivers:staging:nvec:nvec.h Fix typos in staging:nvec Justin P. Mattock
2012-03-26 14:48 ` Greg KH
2012-03-26 15:00 ` Justin P. Mattock [this message]
2012-03-26 16:42 ` Julian Andres Klode
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=4F7084A8.10308@gmail.com \
--to=justinmattock@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.