From: Alan Cox <alan@redhat.com>
To: hch@infradead.org (Christoph Hellwig)
Cc: gerg@snapgear.com (Greg Ungerer),
linux-kernel@vger.kernel.org, alan@redhat.com (Alan Cox)
Subject: Re: Linux 2.5.40-ac1
Date: Thu, 3 Oct 2002 10:20:03 -0400 (EDT) [thread overview]
Message-ID: <200210031420.g93EK3L07983@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021003151707.A17513@infradead.org> from "Christoph Hellwig" at Oct 03, 2002 03:17:07 PM
> The sepearate one is horrible maintaince wise. Please introduce
> CONFIG_MMU and try to make as many _files_ in mm/ conditional on
> those. Else use the proper ways (cond_syscall(), inline stubs) to
> hide the differences.
The two are so different I think that keeping it seperate is actually the
right idea personally. It will be up to the nommu people to chase the "real
computer" mmu code but I don't think that is a problem.
Some of the other areas you really do want to just hide the differences
nicely - eg in proc
next prev parent reply other threads:[~2002-10-03 14:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 23:38 Greg Ungerer
2002-10-03 14:17 ` Christoph Hellwig
2002-10-03 14:20 ` Alan Cox [this message]
2002-10-03 14:51 ` Christoph Hellwig
2002-10-03 15:25 ` Alan Cox
2002-10-03 15:28 ` Christoph Hellwig
2002-10-03 15:31 ` Greg Ungerer
2002-10-03 19:16 ` Rik van Riel
2002-10-03 23:44 ` Greg Ungerer
2002-10-04 0:32 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 14:45 Manfred Spraul
2002-10-03 14:50 ` David S. Miller
2002-10-03 15:18 ` Manfred Spraul
2002-10-03 15:15 ` David S. Miller
2002-10-03 15:48 ` Alan Cox
2002-10-03 15:53 ` Manfred Spraul
2002-10-03 15:17 ` Alan Cox
2002-10-03 15:34 ` Manfred Spraul
2002-10-02 22:18 Alan Cox
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=200210031420.g93EK3L07983@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=gerg@snapgear.com \
--cc=hch@infradead.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
all inboxes | Powered by JetHome®