From: Rob Landley <rob@landley.net>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>,
gerg@uclinux.org
Subject: Re: m68k with mmu doesn't compile after 66d857b08b8c3ed
Date: Tue, 23 Aug 2011 06:57:45 -0500 [thread overview]
Message-ID: <4E5395B9.9010005@landley.net> (raw)
In-Reply-To: <4E51CF9A.7060407@snapgear.com>
On 08/21/2011 10:40 PM, Greg Ungerer wrote:
>> JFYI, it builds fine for all "actual m68ks" (with MMU) I'm interested in.
>> And I guess Greg will say the same for Coldfire and "actual m68ks"
>> without
>> MMU...
>
> Yes :-)
> And from time to time I build all the defconfigs (so both MMU and
> non-MMU) in arch/m68k/configs/. I thought they all worked on 3.0
> if using an appropriate tool chain.
Sorry, building fine now. As I replied earlier, my .config got
truncated in the move from 2.6.39 to 3.0. My bad.
Rob
next prev parent reply other threads:[~2011-08-23 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 19:18 m68k with mmu doesn't compile after 66d857b08b8c3ed Rob Landley
2011-08-20 19:46 ` Geert Uytterhoeven
2011-08-20 22:22 ` Rob Landley
2011-08-22 3:40 ` Greg Ungerer
2011-08-23 11:57 ` Rob Landley [this message]
2011-08-20 20:14 ` Rob Landley
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=4E5395B9.9010005@landley.net \
--to=rob@landley.net \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox