From: David Howells <dhowells@redhat.com>
To: "Mike Frysinger" <vapier.adi@gmail.com>
Cc: "Pekka J Enberg" <penberg@cs.helsinki.fi>,
"Andrew Morton" <akpm@linux-foundation.org>,
bryan.wu@analog.com, linux-kernel@vger.kernel.org,
"Hugh Dickins" <hugh@veritas.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH -mm] Revoke core code: fix nommu arch compiling error bug
Date: Tue, 27 Mar 2007 20:06:28 +0100 [thread overview]
Message-ID: <26771.1175022388@redhat.com> (raw)
In-Reply-To: <8bd0f97a0703271000x2910b2fan573fd37bb45a058d@mail.gmail.com>
Mike Frysinger <vapier.adi@gmail.com> wrote:
> > That sounds reasonable. However, I suspect that most NOMMU CPUs won't be
> > able to do that. In effect you're creating a third option, I think (MMU,
> > NOMMU, MPU).
>
> sure, but i'm not sure the MPU option would be mutually exclusive with
> NOMMU ... in the Blackfin case, we'd want both ...
I imagine that MPU would be a superset of NOMMU.
David
next prev parent reply other threads:[~2007-03-27 19:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:23 [PATCH -mm] Revoke core code: fix nommu arch compiling error bug Wu, Bryan
2007-03-26 10:37 ` Pekka J Enberg
2007-03-26 10:41 ` Andrew Morton
2007-03-26 11:25 ` David Howells
2007-03-26 11:30 ` Pekka J Enberg
2007-03-26 11:44 ` David Howells
2007-03-26 11:55 ` Pekka J Enberg
2007-03-26 12:22 ` David Howells
2007-03-26 12:37 ` Pekka J Enberg
2007-03-26 13:24 ` David Howells
2007-03-26 20:21 ` Mike Frysinger
2007-03-27 3:29 ` Wu, Bryan
2007-03-27 6:57 ` Pekka J Enberg
2007-03-27 7:20 ` Mike Frysinger
2007-03-27 10:05 ` David Howells
2007-03-27 17:00 ` Mike Frysinger
2007-03-27 19:06 ` David Howells [this message]
2007-03-26 13:03 ` Alan Cox
2007-03-26 11:50 ` Andrew Morton
2007-03-26 11:58 ` David Howells
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=26771.1175022388@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bryan.wu@analog.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=vapier.adi@gmail.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 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.