All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	"Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: [patch] kill off PC9800
Date: Mon, 17 May 2004 13:15:37 -0400	[thread overview]
Message-ID: <40A8F339.8030908@pobox.com> (raw)
In-Reply-To: <1084743514.10765.22.camel@mulgrave>

James Bottomley wrote:
> On Sun, 2004-05-16 at 16:28, Jeff Garzik wrote:
> 
>>Although I like deleting things as much as the next guy :) I do have a 
>>question, to which I haven't come up with a good answer myself:
>>
>>Should PC9800 be excised en masse, or just toss the obviously broken or 
>>not-in-any-makefile/Kconfig pieces?
>>
>>The PC9800 net driver stuff still seems to build, and be sane.
> 
> 
> I haven't looked at the net stuff but if it's like the SCSI stuff, it's
> only usable in a pc9800.  The vanilla kernel currently has no way to
> select a pc9800 subarchitecture build.
> 
> This is a test of interest.  Since the pc9800 can't build the vanilla
> kernel, is anyone maintaining the out of tree pieces to allow it to
> build, and would they take on the job of maintaining it in-tree? if
> no-one's interested in maintaining the pc9800 subarchitecture
> components, it stands to reason that no-one is going to be compiling or
> running the net or scsi drivers, so there's no point keeping them
> hanging around.  Thus, if one piece goes, they all should.


Yeah, I suppose I agree, though I dislike removing it en masse for some 
reason.  No real technical reason, more just gut feeling...  The PC9800 
people spent a good long while working with Alan and others to get what 
little bits got merged into the kernel.

I suppose disappearing and not maintaining the code is the overriding 
factor here...

	Jeff




  reply	other threads:[~2004-05-17 17:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 17:50 [patch] kill off PC9800 James Bottomley
2004-05-16 21:21 ` Andrew Morton
2004-05-16 21:28   ` Jeff Garzik
2004-05-16 21:38     ` James Bottomley
2004-05-17 17:15       ` Jeff Garzik [this message]
2004-05-18 20:14   ` Matt Mackall
2004-05-18 20:23     ` Brian Gerst
2004-05-18 20:53       ` Matt Mackall
2004-05-18 21:14         ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2004-05-16  7:35 Norman Diamond
2004-05-16 16:36 ` Adrian Bunk
2004-05-17 21:38   ` Norman Diamond
2004-05-17 21:51     ` Roland Dreier
2004-05-17 21:59       ` Norman Diamond
2004-05-17 22:33         ` Bartlomiej Zolnierkiewicz
2004-05-18  1:04         ` viro
2004-05-17 22:17       ` Joel Jaeggli
2004-05-16  6:21 Randy.Dunlap
2004-05-16  6:28 ` Andrew Morton
2004-05-16 16:16   ` GOTO Masanori
2004-05-16 17:25     ` Randy.Dunlap

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=40A8F339.8030908@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.