public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW ARCHITECTURE FOR 2.5.6] support for NCR voyager
Date: Thu, 14 Mar 2002 15:11:18 +0000	[thread overview]
Message-ID: <20020314151118.A11178@suse.de> (raw)
In-Reply-To: <200203120404.g2C44mV12800@localhost.localdomain>
In-Reply-To: <200203120404.g2C44mV12800@localhost.localdomain>

On Mon, Mar 11, 2002 at 11:04:48PM -0500, James Bottomley wrote:
 > The major change since the last voyager patch is that the voyager code is 
 > split out into an arch/i386/voyager directory which hooks into the main line 
 > code rather than being mixed with it.
 > 
 > The patch is in two parts this time:  The i386 sub-architecture split is 
 > separated from the addition of the voyager components

 Hi James,
  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/ 

-- 
Dave Jones.                    http://www.codemonkey.org.uk
SuSE Labs.

  reply	other threads:[~2002-03-14 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12  4:04 [PATCH: NEW ARCHITECTURE FOR 2.5.6] support for NCR voyager James Bottomley
2002-03-14 15:11 ` Dave Jones [this message]
2002-03-17  3:24   ` 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=20020314151118.A11178@suse.de \
    --to=davej@suse.de \
    --cc=James.Bottomley@HansenPartnership.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