public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Dave Jones <davej@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW ARCHITECTURE FOR 2.5] support for NCR voyager  343x/345x/4100/51xx architecture
Date: Thu, 27 Dec 2001 08:09:45 -0600	[thread overview]
Message-ID: <200112271409.fBRE9kR19806@localhost.localdomain> (raw)
In-Reply-To: Message from Dave Jones <davej@suse.de>  of "Mon, 24 Dec 2001 01:10:43 +0100." <Pine.LNX.4.33.0112240106490.17860-100000@Appserv.suse.de>

davej@suse.de said:
> I'd be *so* much happier to see your patch with setup-voyager.c, and a
> single ifdef in setup.c wrapping setup_voyager() or the likes.

> On another related topic, the bootmem stuff in setup.c would be so
> much nicer to be split into a bootmem.c imho.

> This would also make sharing the x86 bootmem code with the x86-64
> bootmem code a lot simpler. 

Separation is clearly a better way to go.  I'll see what I can do (and whether 
I can take the visw along too). Where is the x86-64 code?  I haven't seen it 
since 2.4.13-ac8.

James Bottomley



  reply	other threads:[~2001-12-27 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-23 19:13 [PATCH: NEW ARCHITECTURE FOR 2.5] support for NCR voyager 343x/345x/4100/51xx architecture James Bottomley
2001-12-24  0:10 ` Dave Jones
2001-12-27 14:09   ` James Bottomley [this message]
2001-12-27 15:33     ` Dave Jones
2001-12-24  0:58 ` Rik van Riel
2001-12-27 14:08   ` James Bottomley
2001-12-27 15:34     ` Dave Jones

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=200112271409.fBRE9kR19806@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox