From: justinmattock@gmail.com (Justin P. Mattock)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/5]arch/arm/common/Makefile Remove unused config in the Makefile.
Date: Thu, 07 Apr 2011 16:40:54 -0700 [thread overview]
Message-ID: <4D9E4B86.1030102@gmail.com> (raw)
In-Reply-To: <20110407222348.GE17049@n2100.arm.linux.org.uk>
On 04/07/2011 03:23 PM, Russell King - ARM Linux wrote:
> On Wed, Apr 06, 2011 at 08:10:36AM -0700, Justin P. Mattock wrote:
>> o.k.!! Thanks for having a look at this..
>
> Could you queue this up in the patch system with everyone's acks please?
> You don't need to include a Cc line for any of my addresses (and I'd
> prefer it not to be in submissions.)
>
> Thanks.
>
o.k. I resent.. hopefully I got the addresses proper.
Justin P. Mattock
next prev parent reply other threads:[~2011-04-07 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 16:58 [RFC 1/5]arch/arm/common/Makefile Remove unused config in the Makefile Justin P. Mattock
2011-04-06 8:05 ` Uwe Kleine-König
2011-04-06 15:10 ` Justin P. Mattock
2011-04-07 22:23 ` Russell King - ARM Linux
2011-04-07 23:40 ` Justin P. Mattock [this message]
2011-04-07 3:59 ` Jean-Christophe PLAGNIOL-VILLARD
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=4D9E4B86.1030102@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).