linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	ide <linux-ide@vger.kernel.org>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] libata: remove experimental tag on PATA drivers
Date: Fri, 13 Nov 2009 17:15:24 +0100	[thread overview]
Message-ID: <200911131715.24377.bzolnier@gmail.com> (raw)
In-Reply-To: <4AFCC0D4.9020708@gmail.com>

On Friday 13 November 2009 03:13:40 Robert Hancock wrote:
> Remove the experimental tag on Parallel ATA drivers. Though some of the
> individual PATA drivers are still marked as experimental, as a group they can
> hardly be considered to be, given they've been used in various distros for some
> time.
> 
> Signed-off-by: Robert Hancock <hancockrwd@gmail.com>

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

PATA_ALI: EXPERIMENTAL
- ATAPI DMA is still broken

PATA_CMD64X: EXPERIMENTAL
- potential data corruption issues remains unfixed for CMD64[3,6]

PATA_SIS: EXPERIMENTAL
- missing MWDMA support on newer controllers

They are all old & known problems and not present in
[ "old", "deprecated", "legacy" ] counterparts.

> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
> index f2df6e2..33133c6 100644
> --- a/drivers/ata/Kconfig
> +++ b/drivers/ata/Kconfig
> @@ -3,7 +3,7 @@
>  #
>  
>  menuconfig ATA
> -	tristate "Serial ATA (prod) and Parallel ATA (experimental) drivers"
> +	tristate "Serial ATA and Parallel ATA drivers"
>  	depends on HAS_IOMEM
>  	depends on BLOCK
>  	depends on !(M32R || M68K) || BROKEN

-- 
Bartlomiej Zolnierkiewicz

  parent reply	other threads:[~2009-11-13 16:16 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 [this message]
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
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=200911131715.24377.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).