From: Jeff Garzik <jgarzik@pobox.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Dan Kegel <dank@kegel.com>,
Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
john slee <indigoid@higherplane.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why can't Johnny compile?
Date: Tue, 19 Nov 2002 11:36:34 -0500 [thread overview]
Message-ID: <3DDA6892.3040709@pobox.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1021119112734.32451A-100000@gatekeeper.tmr.com>
Bill Davidsen wrote:
> If we add a BROKEN category, would you agree that it is a more accurate
> description of the status? I'm not asking that this be back-ported to 2.4,
> but I think of OBSOLETE describing the nec pre-symbios drivers or similar
> things. Or the aha152x driver which I still can't get going in 2.5 :-(
>
It's still early in the 2.5.x game to do this.
next prev parent reply other threads:[~2002-11-19 16:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 5:35 Dan Kegel
2002-11-16 5:49 ` Jeff Garzik
2002-11-16 6:04 ` Patrick Finnegan
2002-11-16 6:10 ` Jeff Garzik
2002-11-16 6:15 ` William Lee Irwin III
2002-11-17 5:34 ` Ralf Baechle
2002-11-16 9:47 ` Kai Henningsen
2002-11-16 14:37 ` Arnaldo Carvalho de Melo
2002-11-16 15:11 ` john slee
2002-11-16 21:04 ` Jeff Garzik
2002-11-16 21:37 ` Arnaldo Carvalho de Melo
2002-11-16 21:42 ` Arnaldo Carvalho de Melo
2002-11-16 23:51 ` Alan Cox
2002-11-17 0:09 ` Dan Kegel
2002-11-17 0:08 ` romieu
2002-11-17 3:18 ` Patrick Finnegan
2002-11-17 0:18 ` Nathan
2002-11-17 0:43 ` Alan Cox
2002-11-18 21:02 ` Bill Davidsen
2002-11-18 23:12 ` Alan Cox
2002-11-19 16:30 ` Bill Davidsen
2002-11-19 16:36 ` Jeff Garzik [this message]
2002-11-19 17:29 ` Alan Cox
2002-11-19 18:01 ` David G Hamblen
2002-11-19 19:34 ` Alan Cox
2002-11-17 1:34 ` Adam Kropelin
2002-11-16 6:23 ` Arnaldo Carvalho de Melo
2002-11-16 19:14 ` Nathan
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=3DDA6892.3040709@pobox.com \
--to=jgarzik@pobox.com \
--cc=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dank@kegel.com \
--cc=davidsen@tmr.com \
--cc=indigoid@higherplane.net \
--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
Powered by JetHome