From: Krzysztof Halasa <khc@pm.waw.pl>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] cleanup Serial ATA and Parallel ATA Kconfig
Date: Sat, 09 Aug 2008 00:58:22 +0200 [thread overview]
Message-ID: <m3sktfw1v5.fsf@maximus.localdomain> (raw)
In-Reply-To: <njhp94pr4ha1nfgmj11n662enalpd9663h@4ax.com> (Grant Coady's message of "Sat\, 09 Aug 2008 08\:34\:40 +1000")
Grant Coady <grant_lkml@dodo.com.au> writes:
> ¦ ¦ --- Serial ATA (SATA) and Parallel ATA (PATA) drivers ¦ ¦
> ¦ ¦ <*> AHCI SATA support ¦ ¦
> ¦ ¦ [*] ATA ACPI Support ¦ ¦
> ¦ ¦ [ ] SATA Port Multiplier support ¦ ¦
> ¦ ¦ < > Silicon Image 3124/3132 SATA support ¦ ¦
> ¦ ¦ [*] ATA SFF support ¦ ¦
> ¦ ¦ *** Serial ATA drivers *** ¦ ¦
> ¦ ¦ < > Initio 162x SATA support ¦ ¦
> ¦ ¦ < > Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support ¦ ¦
As noted, it's both PATA and SATA. People searching for PATA-only PIIX
support may have trouble locating it under SATA.
Why not remove ATA SFF support visual option (or leave it for optional
off-tree drivers only, if it makes sense) and SELECT it when any
driver using it is selected? I'm not sure that users know they need
SFF, or what's that.
I think I would also ask for PATA and for SATA first:
[*] PATA support
[*] SATA support
... PATA drivers if "PATA support" is selected
... SATA drivers if "SATA support" is selected
... PIIX is PATA and/or SATA support is selected
I guess all PATA and/or SATA drivers in a single sorted list (so PIIX
doesn't break ordering).
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-08-08 22:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 16:32 worth separating serial from parallel ATA kernel options? Robert P. J. Day
2008-08-08 16:26 ` Alan Cox
2008-08-08 16:53 ` Robert P. J. Day
2008-08-08 22:34 ` [RFC PATCH] cleanup Serial ATA and Parallel ATA Kconfig Grant Coady
2008-08-08 22:58 ` Krzysztof Halasa [this message]
2008-08-08 23:13 ` Robert P. J. Day
2008-08-09 9:33 ` Alan Cox
2008-08-09 10:39 ` Robert P. J. Day
2008-08-09 12:04 ` Krzysztof Halasa
2008-08-09 12:18 ` Andreas Schwab
2008-08-09 12:36 ` Mikael Pettersson
2008-08-09 13:10 ` Alan Cox
2008-08-09 19:12 ` Krzysztof Halasa
2008-08-09 20:59 ` Alan Cox
2008-08-10 1:07 ` [RFC PATCH] cleanup Serial ATA and Parallel ATA Kconfig try2 Grant Coady
2008-08-10 7:10 ` [RFC PATCH] cleanup Serial ATA and Parallel ATA Kconfig try3 Grant Coady
2008-08-10 7:32 ` Grant Coady
2008-08-10 8:30 ` [RFC PATCH] cleanup Serial ATA and Parallel ATA Kconfig try4 Grant Coady
2008-08-10 9:27 ` Grant Coady
2008-08-10 11:57 ` Oliver Pinter
2008-08-10 23:29 ` Grant Coady
2008-08-09 22:40 ` [RFC PATCH] cleanup Serial ATA and Parallel ATA Kconfig Oliver Pinter
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=m3sktfw1v5.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=rpjday@crashcourse.ca \
/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®