mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Dave Jones <davej@suse.de>,
	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: Thu, 13 Jun 2002 20:13:26 -0400	[thread overview]
Message-ID: <200206140013.g5E0DQR25561@localhost.localdomain> (raw)
In-Reply-To: Message from Dave Jones <davej@suse.de>  of "Fri, 14 Jun 2002 01:17:09 +0200." <20020614011709.E16772@suse.de>

davej@suse.de said:
> Would it make sense for the subarchs to use the generic code where
> possible, and only reimplement it's own (for eg) apic.c as and when it
> actually *needs* to be different ? 

That is really the way I've implemented it.  The only PC specific file in the 
generic directory is mpparse.c (since neither visws nor voyager has an MP 
compliant bios).  All the shareable files are kept in `kernel' and activated 
by config options.

I can certainly move mpparse.c back to kernel and add an extra (non user 
visible) config option.

> Sounds quite logical. What does the current patches you have do ? I've
> not had chance to look at them yet. 

It creates directories `generic' for the standard pc and `visws'.  The voyager 
patch creates a `voyager' directory.  Alternatively, these could be `mach-pc', 
`mach-visws' and `mach-voyager'.

James





  reply	other threads:[~2002-06-14  0:13 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 [this message]
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

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=200206140013.g5E0DQR25561@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®