From: Jeff Garzik <jeff@garzik.org>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata: why do we need to define ATA_ENABLE_PATA instead of a CONFIG option?
Date: Tue, 07 Mar 2006 00:18:58 -0500 [thread overview]
Message-ID: <440D17C2.60200@garzik.org> (raw)
In-Reply-To: <20060307010444.GA6799@localhost.localdomain>
Ravikiran G Thirumalai wrote:
> Currently, we can use the piix ide driver for Intel ICH5 IDE controllers, or
> use ata_piix (libata) by #defining ATA_ENABLE_PATA manually at
> inclulde/linux/libata.h. Why not have a CONFIG option to enable libata for such
> drivers instead of a #define in the code? I was wondering if there is any
> reason it is done this way.
ATA_ENABLE_PATA is there because PATA was highly experimental for a
while, and only developers and power users should be enabling it.
Jeff
next prev parent reply other threads:[~2006-03-07 5:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 1:04 libata: why do we need to define ATA_ENABLE_PATA instead of a CONFIG option? Ravikiran G Thirumalai
2006-03-07 5:18 ` Jeff Garzik [this message]
2006-03-07 6:00 ` Ravikiran G Thirumalai
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=440D17C2.60200@garzik.org \
--to=jeff@garzik.org \
--cc=kiran@scalex86.org \
--cc=linux-ide@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).