From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org, "Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: [patch] kill off PC9800
Date: Sun, 16 May 2004 17:28:44 -0400 [thread overview]
Message-ID: <40A7DD0C.7010007@pobox.com> (raw)
In-Reply-To: <20040516142123.2fd8611b.akpm@osdl.org>
Andrew Morton wrote:
> Well it's a question of whether we're likely to see increasing demand for
> [pc9800] in the future. If so then it would be prudent to put some effort into
> fixing it up rather than removing it.
>
> Seems that's not the case. I don't see a huge rush on this but if after
> this discussion nobody steps up to take care of the code over the next few
> weeks, it's best to remove it.
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.
Jeff
next prev parent reply other threads:[~2004-05-16 21:28 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 [this message]
2004-05-16 21:38 ` James Bottomley
2004-05-17 17:15 ` Jeff Garzik
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=40A7DD0C.7010007@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox