public inbox for linux-kernel@vger.kernel.org
 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@vger.kernel.org,
	davej@redhat.com
Subject: Re: [PATCH] libata: fix broken Kconfig setup
Date: Mon, 17 Oct 2005 13:11:08 -0400	[thread overview]
Message-ID: <4353DB2C.10905@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510170946250.23590@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Mon, 17 Oct 2005, Linus Torvalds wrote:
> 
>>> And then with the quirk issue out of
>>>the way, CONFIG_SCSI_SATA becomes purely a boolean enable/disable-this-menu
>>>switch.
>>
>>No it does not. You continue to ignore the fact that it's not an 
>>enable/disable thing. It's a "can we enable SATA drivers" vs "can we 
>>enable SATA drivers as modules" vs "do we do any SATA drivers at all?" 
>>thing.
>>
>>A tristate.
> 
> 
> Btw, if you want to have the _question_ always be y/n only, that's easy 
> enough to do, just make that one do
> 
> 	config SATA_MENU
> 		bool "Want to see SATA drivers"
> 		depends on SCSI != n
> 
> 	config SCSI_SATA
> 		tristate
> 		depends on SCSI && SATA_MENU
> 		default y
> 
> and now you have a totally sensible setup, where the low-level drivers can 
> depend on something sane. 
> 
> I don't think it _buys_ you anything, but hey, at least it's logical. 

That's a reasonable solution.  I think it does buy you reduced user 
confusion.


> Btw, wouldn't it be much nicer to also have this all in a totally separate 
> Kconfig file? That SCSI Kconfig file is one of the biggest ones (yeah, 
> drivers/net/Kconfig is bigger, but hey, that's not a surprise, is it ;)

Honestly, I've been pondering moving all libata drivers to drivers/ata 
anyway...

	Jeff




  reply	other threads:[~2005-10-17 17:11 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 [this message]
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
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=4353DB2C.10905@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --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