From: James Bottomley <James.Bottomley@SteelEye.com>
To: Dave Jones <davej@suse.de>,
James Bottomley <James.Bottomley@SteelEye.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrey Panin <pazke@orbita1.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series)
Date: Sat, 15 Jun 2002 20:00:25 -0400 [thread overview]
Message-ID: <200206160000.g5G00PX24105@localhost.localdomain> (raw)
In-Reply-To: Message from Andrey Panin <pazke@orbita1.ru> of "Fri, 14 Jun 2002 17:41:52 +0400." <20020614134152.GA1293@pazke.ipt>
pazke@orbita1.ru said:
> "Latest" (2.4.17) visws patch which i'm planning to convert for 2.5,
> uses function MP_processor_info() from generic mpparse.c. May be it
> makes sence to move to some generic file ?
OK, I moved mpparse back into kernel (and gated it on CONFIG_X86_MPPARSE). It
probably makes sense to split it up so that you only get the piece you need
for visws.
I've also done the mach-* renames by popular request. The new patch is at:
http://www.hansenpartnership.com/voyager/files/arch-split-2.5.21-II.diff
and also in the bitkeeper repository:
http://linux-voyager.bkbits.net/arch-split-2.5
James
prev parent reply other threads:[~2002-06-16 0:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 17:54 James Bottomley
2002-06-13 8:20 ` Andrey Panin
2002-06-13 15:48 ` James Bottomley
2002-06-13 23:17 ` Dave Jones
2002-06-14 0:13 ` James Bottomley
2002-06-14 0:45 ` Dave Jones
2002-06-14 2:19 ` Matthew D. Pitts
2002-06-14 2:52 ` SCSI host/channel/lun/part to /dev/sd* or maj/minor mapping Mark Atwood
2002-06-14 13:41 ` [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series) Andrey Panin
2002-06-14 13:49 ` Dave Jones
2002-06-14 13:52 ` Andrey Panin
2002-06-14 14:14 ` James Bottomley
2002-06-14 14:16 ` Dave Jones
2002-06-17 13:36 ` Andrey Panin
2002-06-17 14:03 ` Dave Jones
2002-06-16 0:00 ` 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=200206160000.g5G00PX24105@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@orbita1.ru \
/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®