From: Greg Ungerer <gerg@snapgear.com>
To: Greg Ungerer <gerg@uclinux.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Tim Abbott <tabbott@ksplice.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 08/20] m68knommu: change to new flag variables
Date: Tue, 28 Sep 2010 23:22:22 +1000 [thread overview]
Message-ID: <4CA1EC0E.2020304@snapgear.com> (raw)
In-Reply-To: <20100928071606.GA13303@haskell.muteddisk.com>
Hi Matt,
On 28/09/10 17:16, matt mooney wrote:
> On 16:41 Tue 28 Sep , Greg Ungerer wrote:
>>
>> Hi Matt,
>>
>> On 23/09/10 16:50, matt mooney wrote:
>>> Replace EXTRA_CFLAGS with ccflags-y and EXTRA_AFLAGS with asflags-y.
>>>
>>> Signed-off-by: matt mooney<mfm@muteddisk.com>
>>
>> Looks fine to me. Are you looking for this to go through
>> maintainer trees, or the whole patch series in one go?
>
> Hi Greg,
>
> My original intent was through the maintainer trees; however, I am starting to
> realize that it probably would have been best to all go into the kbuild tree as
> one patch series. That being said, some people have picked them up and others
> have just acked, so really whatever is easiest for you. All unapplied will
> eventually go through the kbuild tree.
I am happy to pick up the m68knommu change and send up-stream.
Regards
Greg
>> Acked-by: Greg Ungerer<gerg@uclinux.org>
>>
>> Regards
>> Greg
>>
>>
>>> ---
>>> arch/m68knommu/platform/5206/Makefile | 4 ++--
>>> arch/m68knommu/platform/5206e/Makefile | 4 ++--
>>> arch/m68knommu/platform/520x/Makefile | 4 ++--
>>> arch/m68knommu/platform/523x/Makefile | 4 ++--
>>> arch/m68knommu/platform/5249/Makefile | 4 ++--
>>> arch/m68knommu/platform/5272/Makefile | 4 ++--
>>> arch/m68knommu/platform/527x/Makefile | 4 ++--
>>> arch/m68knommu/platform/528x/Makefile | 4 ++--
>>> arch/m68knommu/platform/5307/Makefile | 4 ++--
>>> arch/m68knommu/platform/532x/Makefile | 4 ++--
>>> arch/m68knommu/platform/5407/Makefile | 4 ++--
>>> arch/m68knommu/platform/coldfire/Makefile | 4 ++--
>>> 12 files changed, 24 insertions(+), 24 deletions(-)
>>>
next prev parent reply other threads:[~2010-09-28 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 6:50 [PATCH 08/20] m68knommu: change to new flag variables matt mooney
2010-09-28 6:41 ` Greg Ungerer
2010-09-28 7:16 ` matt mooney
2010-09-28 13:22 ` Greg Ungerer [this message]
2010-09-29 14:36 ` Michal Marek
2010-09-29 23:15 ` matt mooney
2010-09-30 20:51 ` Michal Marek
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=4CA1EC0E.2020304@snapgear.com \
--to=gerg@snapgear.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tabbott@ksplice.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