public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nick Evgeniev" <nick@octet.com>
To: "Andre Hedrick" <andre@linux-ide.org>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.4.19-preX IDE bugs
Date: Tue, 11 Jun 2002 19:31:48 +0400	[thread overview]
Message-ID: <002101c2115d$1c0bc7c0$baefb0d4@nick> (raw)
In-Reply-To: <Pine.LNX.4.10.10206081251300.1190-100000@master.linux-ide.org>

Hi,

> > I added it to the collection of IDE oddities I'm looking at. There are
> > also some promise requested changes due to get merged at the end of this
> > week. Then we can see where we stand
>
> Also, it is hard to answer email without connectivity in the air.

Agreed. But all what I see is that STABLE Linux kernel DOESN'T has working
driver for promise controller (including latest ac patches) for SEVERAL
MONTHS.
And as for now there is no any progress in fixing it. I don't blame on you,
or Alan,
or whoever else. All I have to suggest is to drop promise support in stable
kernel,
then rewrite/fix it in 2.5 tree... and then backport it to 2.4.

I don't want to make experiments in production environment anymore... And
it's
unfair to the rest of Linux users to keep broken drivers in stable kernel...
Because
nobody expects that stable kernel will rip your fs _daily_.




  reply	other threads:[~2002-06-11 15:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 15:28 linux 2.4.19-preX IDE bugs Nick Evgeniev
2002-06-04 16:41 ` Alan Cox
2002-06-08 19:52   ` Andre Hedrick
2002-06-11 15:31     ` Nick Evgeniev [this message]
2002-06-11 16:52       ` Andre Hedrick
2002-06-13 11:15         ` Nick Evgeniev
2002-06-14  7:01           ` Andre Hedrick
2002-06-14  7:44             ` Nick Evgeniev
2002-06-14  8:20               ` Andre Hedrick
2002-06-14  8:37                 ` Vojtech Pavlik
2002-06-14  8:45                   ` Andre Hedrick
2002-06-14  8:55                     ` Vojtech Pavlik
2002-06-14  8:59                       ` Andre Hedrick
2002-06-14  9:15                         ` Bartlomiej Zolnierkiewicz
2002-06-14  9:19                         ` Bartlomiej Zolnierkiewicz
2002-06-14  8:59                     ` Abraham vd Merwe
2002-06-14  9:08                       ` Andre Hedrick
2002-06-14  9:24                         ` Abraham vd Merwe
2002-06-14  9:06                 ` Nick Evgeniev
2002-06-11 18:53       ` Jason C. Pion
2002-06-11 19:34         ` Tomas Szepe
2002-06-11 19:47           ` Jason C. Pion
2002-06-14 12:34         ` Bill Davidsen
2002-06-14 14:22           ` Jason C. Pion
2002-06-11 22:49       ` Bill Davidsen
2002-06-12  0:19         ` Andre Hedrick
2002-06-12  7:31         ` Alan Cox
2002-06-12 13:57           ` Bill Davidsen
2002-06-12 18:32             ` Andre Hedrick
2002-06-12 20:30               ` Bill Davidsen
2002-06-12  7:36       ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-06-11 18:26 Mikael Pettersson
2002-06-13 20:39 Mikael Pettersson
2002-06-15 17:12 Anssi Saari
2002-06-15 18:51 ` Vojtech Pavlik

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='002101c2115d$1c0bc7c0$baefb0d4@nick' \
    --to=nick@octet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@octet.spb.ru \
    /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