From: James Bottomley <James.Bottomley@steeleye.com>
To: Dave Jones <davej@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-kernel@vger.kernel.org, mochel@odsl.org
Subject: Re: [PATCH: NEW ARCHITECTURE FOR 2.5.6] support for NCR voyager
Date: Sat, 16 Mar 2002 22:24:21 -0500 [thread overview]
Message-ID: <200203170324.g2H3OMI02667@localhost.localdomain> (raw)
In-Reply-To: Message from Dave Jones <davej@suse.de> of "Thu, 14 Mar 2002 15:11:18 GMT." <20020314151118.A11178@suse.de>
davej@suse.de said:
> I just took a quick look at your work on splitting this stuff up,
> and I
> think it's definitly heading in the right direction. As to
> integrating this,
> I think it's probably best to get Patrick Mochel's other related
> work
> included first. See what he's done so far at..
> http://kernel.org/pub/linux/kernel/people/mochel/patches/
> patch-linux-v2.5.6-pm1.bz2
> His patch and yours touch various files for more or less the same
> reason.
> Patrick still has some bits to finish off here, but combined the two
> patchsets
> will bring some much needed sanity to various parts of arch/i386/
I just finished the combination of the two:
http://www.hansenpartnership.com/voyager/files/split-combine-2.5.6.diff
http://www.hansenpartnership.com/voyager/files/split-combine-2.5.6.BK
Also added the voyager patches
http://www.hansenpartnership.com/voyager/files/voyager-split-combine-2.5.6.diff
http://www.hansenpartnership.com/voyager/files/voyager-split-combine-2.5.6.BK
I've checked that the voyager additions will combine and boot. There seems to
be some problem with missing pci functions which prevent a standard SMP
compile. I think it has to do with a missing entry in the Makefile in
drivers/pci for hotplug.c. I think Patrick probably needs to look at this.
James
prev parent reply other threads:[~2002-03-17 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 4:04 James Bottomley
2002-03-14 15:11 ` Dave Jones
2002-03-17 3:24 ` James Bottomley [this message]
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=200203170324.g2H3OMI02667@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@odsl.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®