From: Krzysztof Halasa <khc@pm.waw.pl>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mikael Pettersson <mikpe@it.uu.se>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ATA Kconfig cleanup: sort the driver list and modify some text
Date: Thu, 21 Aug 2008 02:49:55 +0200 [thread overview]
Message-ID: <m3ljyrqjik.fsf@maximus.localdomain> (raw)
In-Reply-To: <tecpa4928hh8kahc53p019sr7nclg8kbjr@4ax.com> (Grant Coady's message of "Thu\, 21 Aug 2008 10\:16\:49 +1000")
Grant Coady <grant_lkml@dodo.com.au> writes:
>>How the user compiling the kernel knows what ATA_SFF stands for?
>
> They read the help text :)
Well, can't say you're wrong...
>>Why not "select ATA_SFF" instead (when any driver using this is
>>selected)?
>
> Because then the driver list is always visible?
And it's IMHO great. Don't you like the full list immediately when
drivers/ata are selected?
> Besides, I don't like the way select locks in stuff at the moment, means
> you have to turn off every option to get rid of the forced select option
> -- I'd rather see turning off a 'select'ed item drop all of its
> dependencies.
But it's not a problem with drivers/ata, is it?
Personally I think I'd prefer a dialog box listing dependencies and
asking what to do with that, and other improvements. I guess I should
start hacking kconfig some day.
--
Krzysztof Halasa
prev parent reply other threads:[~2008-08-21 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 5:15 [PATCH 1/3] ATA Kconfig cleanup: hide ATA_SFF and add SATA/PATA menu items Grant Coady
2008-08-16 10:01 ` Mikael Pettersson
2008-08-16 10:32 ` Alan Cox
2008-08-17 4:20 ` Jeff Garzik
2008-08-18 1:47 ` [PATCH] ATA Kconfig cleanup: sort the driver list and modify some text Grant Coady
2008-08-18 8:56 ` Alan Cox
2008-08-20 23:27 ` Krzysztof Halasa
2008-08-21 0:16 ` Grant Coady
2008-08-21 0:49 ` Krzysztof Halasa [this message]
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=m3ljyrqjik.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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
all inboxes | Powered by JetHome®