All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH 1/2] move host drivers for VLB IDE controllers to staging/out
Date: Tue, 02 Feb 2010 17:59:54 -0500	[thread overview]
Message-ID: <4B68AE6A.8030304@garzik.org> (raw)
In-Reply-To: <201002022222.29728.bzolnier@gmail.com>

On 02/02/2010 04:22 PM, Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 02 February 2010 07:00:41 pm Alan Cox wrote:
>> On Tue, 02 Feb 2010 18:27:08 +0100
>> Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>  wrote:
>>
>>> From: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>
>>> Subject: [PATCH] move host drivers for VLB IDE controllers to staging/out
>>>
>>> - they are for really old hardware that nobody has any longer
>>> - they all require 'magic' parameters to work
>>> - many controllers are also supported by pata_legacy driver
>>>
>>> so move them to staging/out and schedule for removal in 2.6.36
>>> unless somebody steps in to work on them.
>>>
>>> Signed-off-by: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>
>>
>> Acked-by: Alan Cox<alan@linux.intel.com>
>>
>> When I actually tried some of the VLB bits while working on the
>> pata_legacy stuff it was clear these hadn't been maintained/used for a
>> very long time indeed. Most of them also are hacks doing stuff like fixed
>> mode settings.
>>
>> However if the point of the old IDE code was as claimed to keep it as a
>> 'stable' layer throwing chunks of it out doesn't strike me as in keeping
>> with the stated plan ...
>
> I've always been under the impression that the claim was about adding new
> stuff and not about removing dead code or ongoing efforts to make whole
> kernel more maintainable.  Either way, Dave would be a much better person
> to clarify it..

David's statements at the time were

	I'm going to treat IDE as pure legacy, rather than as
	competition with the PATA drivers which is what people whould
	be moving over to.

	And more importantly I refuse to apply any driver patch that
	isn't actually tested on said hardware.

"pure legacy" does not usually imply accepting major changes to drivers, 
changing APIs, and the like.

But if IDE users are happy with this abrupt change of direction, the 
resumption of frequent, large IDE changes, then that's their call...   I 
would rather they just use libata, but who am I to judge?  ;-)

	Jeff




  reply	other threads:[~2010-02-02 22:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 17:27 [PATCH 0/2] atang update for 02/02/10 Bartlomiej Zolnierkiewicz
2010-02-02 17:27 ` [PATCH 1/2] move host drivers for VLB IDE controllers to staging/out Bartlomiej Zolnierkiewicz
2010-02-02 18:00   ` Alan Cox
2010-02-02 18:00     ` Alan Cox
2010-02-02 21:22     ` Bartlomiej Zolnierkiewicz
2010-02-02 22:59       ` Jeff Garzik [this message]
2010-02-03  0:08         ` Bartlomiej Zolnierkiewicz
2010-02-02 17:27 ` [PATCH 2/2] ide: remove hwif_chipset_t type Bartlomiej Zolnierkiewicz

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=4B68AE6A.8030304@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=davem@davemloft.net \
    --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.