From: gerg <gerg@snapgear.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: linux-2.5.30uc0 MMU-less patches
Date: Sat, 03 Aug 2002 01:54:26 +1000 [thread overview]
Message-ID: <3D4AAB32.8050608@snapgear.com> (raw)
In-Reply-To: 20020802173449.N25761@suse.de
Hi Dave,
Dave Jones wrote:
> On Sat, Aug 03, 2002 at 01:29:55AM +1000, gerg wrote:
> > Yep, there sure is some crap in there :-)
> > Obviously left over from the original copy out
> > from arch/i386/config.in.
> >
> > I have cleaned all that silly stuff out for the
> > next patch.
>
> With the silly nits like that aside, it leaves just the
> more serious 'issues' such as those brought up by Willy
> earlier.
>
> The whole idea of a seperate mmnommu (or was it nommumm/ ?)
> directory seemed a bit odd-looking too. (Asides from the
> horrible name)
It surely is a horrible name :-)
> I didn't check the code in detail, but
> is there really that little that can be shared between
> the regular mm/ ?
No, there is actually a lot in common. Probably something
like 70%. This is really a question of organization.
I would much prefer to see the non-mmu support in with mm.
But it would mean a few #ifdef's in there to allow for
the differences.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Wizard EMAIL: gerg@snapgear.com
Snapgear Pty Ltd PHONE: +61 7 3279 1822
825 Stanley St, FAX: +61 7 3279 1820
Woolloongabba, QLD, 4102, Australia WEB: www.snapgear.com
next prev parent reply other threads:[~2002-08-02 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 6:34 [PATCH]: linux-2.5.30uc0 MMU-less patches Greg Ungerer
2002-08-02 12:16 ` Dave Jones
2002-08-02 15:29 ` gerg
2002-08-02 15:34 ` Dave Jones
2002-08-02 15:54 ` gerg [this message]
2002-08-02 16:01 ` Dave Jones
2002-08-02 14:39 ` David Woodhouse
2002-08-02 16:01 ` gerg
2002-08-05 10:02 ` David Woodhouse
2002-08-05 15:36 ` gerg
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=3D4AAB32.8050608@snapgear.com \
--to=gerg@snapgear.com \
--cc=davej@suse.de \
--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 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.