From: Greg Ungerer <gerg@snapgear.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [uClinux-dev] [PATCH] m68k: merge the mmu and non-mmu kernel/Makefiles
Date: Thu, 11 Aug 2011 16:45:35 +1000 [thread overview]
Message-ID: <4E437A8F.60505@snapgear.com> (raw)
In-Reply-To: <20110811060807.GB21757@merkur.ravnborg.org>
On 11/08/11 16:08, Sam Ravnborg wrote:
> On Thu, Aug 11, 2011 at 02:47:24PM +1000, gerg@snapgear.com wrote:
>> From: Greg Ungerer<gerg@uclinux.org>
>>
>> [This is a resend of this patch. If no-one has any objections then I
>> want to push this into linux-next, for eventual inclusion in the 3.2
>> merge window.]
>>
>> The few differences between the mmu and non-mmu kernel/Makefiles can
>> easily be handled inside of a single Makefile. Merge the 2 back into
>> a single Makefile.
>
> Looks good (except the typo that is nto a typo:-) )
That is a little gem that one :-)
> Acked-by: Sam Ravnborg<sam@ravnborg.org>
Thanks Sam!
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2011-08-11 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 4:47 [PATCH] m68k: merge the mmu and non-mmu kernel/Makefiles gerg
2011-08-11 6:08 ` [uClinux-dev] " Sam Ravnborg
2011-08-11 6:45 ` Greg Ungerer [this message]
2011-08-13 14:27 ` Geert Uytterhoeven
2011-08-15 2:07 ` Greg Ungerer
2011-08-13 16:44 ` Andreas Schwab
2011-08-15 1:12 ` Greg Ungerer
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=4E437A8F.60505@snapgear.com \
--to=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=uclinux-dev@uclinux.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