From: viro@parcelfarce.linux.theplanet.co.uk
To: Christoph Hellwig <hch@infradead.org>,
Jeff Garzik <jgarzik@pobox.com>, Adrian Bunk <bunk@fs.tum.de>,
Andreas Haumer <andreas@xss.co.at>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [2.4 patch] disallow modular CONFIG_COMX
Date: Tue, 13 Jan 2004 10:51:33 +0000 [thread overview]
Message-ID: <20040113105133.GB21151@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040113095711.A15396@infradead.org>
On Tue, Jan 13, 2004 at 09:57:11AM +0000, Christoph Hellwig wrote:
> On Mon, Jan 12, 2004 at 05:24:49PM -0500, Jeff Garzik wrote:
> > I agree with the intent...
> >
> > At this point, I am tempted to simply comment it out of the Config.in,
> > and let interested parties backport bug fixes and crap from 2.6 if they
> > would like. The driver has had obvious bugs for a while...
>
> In 2.6 it's as buggy as in 2.4..
The driver is full of obvious bugs, had been that way for years, has
userland API broken by design and maintainers who couldn't be arsed
to fix it.
By now I don't see how anything short of rm(1) will help that animal.
next prev parent reply other threads:[~2004-01-13 10:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 13:13 Linux 2.4.24-pre3 Marcelo Tosatti
2003-12-31 13:53 ` Tim Cambrant
2003-12-31 15:26 ` Andreas Haumer
2004-01-10 1:39 ` [2.4 patch] fix CONFIG_DS1742 Config.in entry Adrian Bunk
2004-01-11 1:30 ` [2.4 patch] disallow modular CONFIG_COMX Adrian Bunk
2004-01-12 22:24 ` Jeff Garzik
2004-01-13 0:25 ` Adrian Bunk
2004-01-13 9:57 ` Christoph Hellwig
2004-01-13 10:51 ` viro [this message]
2004-01-12 2:10 ` [2.4 patch] simplify PARPORT_PC_PCMCIA dependencies Adrian Bunk
2004-01-13 0:58 ` [2.4 patch] simplify COMX_PROTO_LAPB dependencies Adrian Bunk
2003-12-31 18:51 ` Iostats reporting problems was: Linux 2.4.24-pre3 Mike Fedyk
2004-01-13 1:42 ` Rick Lindsley
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=20040113105133.GB21151@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=andreas@xss.co.at \
--cc=bunk@fs.tum.de \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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®