All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	ide <linux-ide@vger.kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] libata: remove experimental tag on PATA drivers
Date: Sat, 14 Nov 2009 02:08:29 +0100	[thread overview]
Message-ID: <200911140208.29888.bzolnier@gmail.com> (raw)
In-Reply-To: <20091114001510.2dd0ab5d@lxorguk.ukuu.org.uk>

On Saturday 14 November 2009 01:15:10 Alan Cox wrote:
> On Sat, 14 Nov 2009 00:46:29 +0100
> Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> 
> > On Friday 13 November 2009 19:25:15 Alan Cox wrote:
> > > > Fine but please update status of following host drivers that were
> > > > marked as "stable" prematurely by commit e3389cb first:
> > > > 
> > > > PATA_PDC_OLD: needs to be marked as EXPERIMENTAL (or just BROKEN)
> > > > - known reliability problems with UDMA
> > > 
> > > A few odd reports apparently linked to specific chip revs. It's at
> > > least as stable as the old IDE one which doesn't work on my hardware. I'd
> > 
> > Skipping the technical merit of the quoted text for the moment -- I find
> 
> You mean the content ?
> 
> > the fact that you keep calling the present IDE host drivers (that many
> > developers helped to fix) as "old" ones or "buggy" ones rather degrading
> 
> As you quoted the old PDC202xx driver does not work on my test hardware.
> The libata one does. That is what is popularly known as a "fact". I'm not

You want facts?  Here we go:

https://bugzilla.redhat.com/show_bug.cgi?id=250349
https://bugzilla.novell.com/show_bug.cgi?id=457037
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/399616

> entirely happy with either PDC driver for older chips and I've spent
> considerable time grovelling through old drivers, alternate drivers and
> what little documentation exists to try and figure it out in more detail.
> 
> The lost IRQ recovery patches seem to have helped a fair bit, and your
> UDMA33 fix likewise.

I regret this work -- because of it I share the blame for the new driver
and keep getting complains about it..

> > for their (this includes me of course) hard work.
> 
> All because you wouldn't work on the libata ones which had a future. You

The rest of your mail is "the same good old straw-man" to put me back
into specially created for me by you & co. "difficult to work with" box.

Guys, "the devil" has been long out of the box.. :)

-- 
Bartlomiej Zolnierkiewicz

  reply	other threads:[~2009-11-14  1:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  2:13 [PATCH] libata: remove experimental tag on PATA drivers Robert Hancock
2009-11-13 11:07 ` Alan Cox
2009-11-13 16:15 ` Bartlomiej Zolnierkiewicz
2009-11-13 18:25   ` Alan Cox
2009-11-13 19:39     ` Bartlomiej Zolnierkiewicz
2009-11-13 21:30       ` Alan Cox
2009-11-13 22:17         ` Bartlomiej Zolnierkiewicz
2009-11-13 22:42           ` Alan Cox
2009-11-13 22:58             ` Bartlomiej Zolnierkiewicz
2009-11-14  0:03               ` Alan Cox
2009-11-13 21:57       ` Jeff Garzik
2009-11-13 22:24         ` Bartlomiej Zolnierkiewicz
2009-11-13 22:26     ` Alejandro Riveira Fernández
2009-11-13 23:46     ` Bartlomiej Zolnierkiewicz
2009-11-14  0:14       ` Bartlomiej Zolnierkiewicz
2009-11-14  0:15       ` Alan Cox
2009-11-14  1:08         ` Bartlomiej Zolnierkiewicz [this message]
2009-11-14 16:04           ` Alan Cox
2009-11-14 16:59             ` Bartlomiej Zolnierkiewicz
2009-11-14  2:29       ` Matthew Garrett
2009-11-14  2:54         ` Bartlomiej Zolnierkiewicz
2009-11-14 12:02           ` Bartlomiej Zolnierkiewicz
2009-11-17  3:18 ` Jeff Garzik

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=200911140208.29888.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=corbet@lwn.net \
    --cc=hancockrwd@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.