From: Ronald Bultje <rbultje@ronald.bitfreak.net>
To: "Mohammad A . Haque" <mhaque@haque.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jinbo21@hananet.net, linux-kernel@vger.kernel.org
Subject: Re: buz.c of 2.4.4
Date: Mon, 30 Apr 2001 23:15:51 +0200 [thread overview]
Message-ID: <20010430231551.A11965@tux.bitfreak.net> (raw)
In-Reply-To: <E14uI6W-0008Kl-00@the-village.bc.nu> <Pine.LNX.4.33.0104301436280.29480-100000@viper.haque.net>
In-Reply-To: <Pine.LNX.4.33.0104301436280.29480-100000@viper.haque.net>; from mhaque@haque.net on Mon, Apr 30, 2001 at 20:37:39 +0200
On 2001.04.30 20:37:39 +0200 Mohammad A. Haque wrote:
> On Mon, 30 Apr 2001, Alan Cox wrote:
>
> > Buz.c doesnt work build or anything. Once the zoran merge is done it
> will
> > go away, until then I simply dont care. At least its obviously broken
> right
> > now
>
> Can't we just remove it then?
>
> Come to think of it .. then we'd start getting "buz drivers missing"
> reports.
So what?
Refer them to mjpeg-users@lists.sourceforge.net and we'll explain them how
to use the new zoran driver until it's in the official kernel...
I mean, it be worse if they _used_ the old buz-thing, they'd start bugging
you with "how do I fix it?"
A broken driver in the kernel basically means a broken kernel - so it'd be
better to just remove it I guess... What do you think, Alan?
--
Ronald Bultje
next prev parent reply other threads:[~2001-04-30 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 17:23 Byeong-ryeol Kim
2001-04-28 19:56 ` Ronald Bultje
2001-04-30 18:08 ` Alan Cox
2001-04-30 18:37 ` Mohammad A. Haque
2001-04-30 21:15 ` Ronald Bultje [this message]
2001-04-30 21:33 ` Gerd Knorr
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=20010430231551.A11965@tux.bitfreak.net \
--to=rbultje@ronald.bitfreak.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jinbo21@hananet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhaque@haque.net \
/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®