From: Dave Jones <davej@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 arch subdivision into machine types for 2.5.8
Date: Tue, 16 Apr 2002 23:06:45 +0200 [thread overview]
Message-ID: <20020416230645.D32185@suse.de> (raw)
In-Reply-To: <m1r8lfigqc.fsf@frodo.biederman.org> <200204162051.g3GKpDb05800@localhost.localdomain>
On Tue, Apr 16, 2002 at 03:51:12PM -0500, James Bottomley wrote:
> I agree with both of these. The main problem with the memory setup calls is
> that most of them are static. I could export them and do overrides, like I do
> for everything else, but as someone who also debugs the kernel, I like static
> functions because they tell me the use is tightly isolated. I could easily do
> two files, it was just looking more messy.
>
> I'll see if I can export some of the setup.c internals and re-arrange this in
> a more orderly way.
I think this is where Patrick Mochel's recent work in that area is going to
come in handy. setup.c has been nicely abstracted out into seperate
parts, that should make things a little easier.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-04-16 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 15:55 [PATCH] i386 arch subdivision into machine types for 2.5.8 James Bottomley
2002-04-16 16:46 ` Patrick Mochel
2002-04-17 0:55 ` Keith Owens
2002-04-16 19:30 ` Eric W. Biederman
2002-04-16 20:51 ` James Bottomley
2002-04-16 21:06 ` Dave Jones [this message]
2002-04-16 21:44 ` Eric W. Biederman
2002-04-16 23:27 ` James Bottomley
2002-04-16 23:43 ` H. Peter Anvin
2002-04-17 7:00 ` Eric W. Biederman
2002-04-17 16:31 ` James Bottomley
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=20020416230645.D32185@suse.de \
--to=davej@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ebiederm@xmission.com \
--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