All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	ben-linux@fluff.org
Subject: Re: Removal of BAST IDE driver
Date: Wed, 25 Jun 2008 06:31:31 -0400	[thread overview]
Message-ID: <48621E83.3060608@pobox.com> (raw)
In-Reply-To: <200806251214.14749.bzolnier@gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> series) so when later Jeff merged:
> 
> commit cc18e0fea7907e7a96b7df71b81838d518bc074e
> Author: Ben Dooks <ben-linux@fluff.org>
> Date:   Mon Jun 16 12:16:26 2008 +0100
> 
>     LIBATA: Add HAVE_PATA_PLATFORM to select PATA_PLATFORM driver
> ...
> 
> which was patch #1/2 in the series I was under impression that now we
> have both new and old driver with the old driver being the default because
> of the link order.  Seems I was wrong after all as other things are moving
> slower than IDE/ATA. ;)
> 
> Sorry for messing things up.  Russell/Ben: how should we proceed with
> fixing it (arch part in or ide part out)?


Ben's change merely adds a knob that a platform may set, in order to 
enable the existing pata_platform driver, which is pretty safe by itself.

The next piece -- once not in 2.6.26 AFAIK -- is arch-specific code 
selecting HAVE_PATA_PLATFORM.  BAST IDE, I assume, can go away once 
relevant platforms start turning on HAVE_PATA_PLATFORM.

	Jeff



  reply	other threads:[~2008-06-25 10:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  9:09 Removal of BAST IDE driver Russell King
2008-06-25 10:14 ` Bartlomiej Zolnierkiewicz
2008-06-25 10:31   ` Jeff Garzik [this message]
2008-06-25 11:32     ` Russell King

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=48621E83.3060608@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben-linux@fluff.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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.