linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-ide@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] libata: fix broken Kconfig setup
Date: Mon, 17 Oct 2005 13:22:39 -0400	[thread overview]
Message-ID: <4353DDDF.50000@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510171008120.3369@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Mon, 17 Oct 2005, Jeff Garzik wrote:
> 
>>If IDE is compiled in, IDE SATA option is not enabled, and ata_piix or ahci
>>are used.
> 
> 
> How about this diff instead?

Nope, it elides critical logic.

1) The quirk should not be enabled if IDE driver is a module.  No reason 
to perform the nasty hack at all, as the user controls module load order.

2) The quirk should not be enabled if IDE driver is not built at all. 
Standard resource reservation code works as expected here.

3) The quirk should not be enabled if CONFIG_BLK_DEV_IDE_SATA is 
enabled, which indicates that the IDE driver gets preference for the 
Intel SATA hardware in question.


> It's really quite clean and understandable, and it makes it very clear 
> what's going on from a configuration standpoint, imnsho. And it does the 
> right thing when AHCI/PIIX is compiled as a SATA module (well, as right as 
> this approach ever can).

My patch works fine when ahci/piix is compiled as a module.  That's the 
configuration I personally tested.


> Of course, somebody should check that it really is just the AHCI and PIIX 
> drivers that want the quirk,

It is.  I wrote 100% of the code, and further, the quirk specifically 
enumerates which PCI IDs are affected, making it easy to verify.

	Jeff

  reply	other threads:[~2005-10-17 17:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17  4:46 [PATCH] libata: fix broken Kconfig setup Jeff Garzik
2005-10-17 11:10 ` Matthias Urlichs
2005-10-17 11:20   ` Jeff Garzik
2005-10-17 15:14 ` Linus Torvalds
2005-10-17 15:32   ` Jeff Garzik
2005-10-17 15:58     ` Linus Torvalds
2005-10-17 16:21       ` Jeff Garzik
2005-10-17 16:38         ` Linus Torvalds
2005-10-17 16:53           ` Linus Torvalds
2005-10-17 17:11             ` Jeff Garzik
2005-10-17 17:25               ` Linus Torvalds
2005-10-17 17:38                 ` Jeff Garzik
2005-10-19 11:49                 ` Alistair John Strachan
2005-10-19 16:02                   ` Randy.Dunlap
2005-10-17 17:01           ` Jeff Garzik
2005-10-18 11:15             ` Sergey Vlasov
2005-10-18 20:56               ` Jeff Garzik
2005-10-17 17:12         ` Linus Torvalds
2005-10-17 17:22           ` Jeff Garzik [this message]
2005-10-17 16:52   ` Jesse Barnes
2005-10-17 17:03     ` Jeff Garzik
2005-10-17 17:06       ` Jesse Barnes
2005-10-17 17:16         ` Jeff Garzik
2005-10-20 14:14         ` Alan Cox
2005-10-20 16:45           ` Jesse Barnes

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=4353DDDF.50000@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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).