[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46EBDBE8.6070201@s5r6.in-berlin.de>
Date: Sat, 15 Sep 2007 15:19:36 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Adrian Bunk <bunk@...nel.org>
CC: Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
James Bottomley <james.bottomley@...eleye.com>,
linux-scsi@...r.kernel.org, Jeff Garzik <jeff@...zik.org>,
Andi Kleen <andi@...stfloor.org>,
Folkert van Heusden <folkert@...heusden.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI
core's widespread usage
Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 11:14:21PM +0200, Stefan Richter wrote:
>> + You need it
>> + - for classic parallel SCSI hardware,
>> + - for newer SCSI transports such as Fibre Channel, FireWire storage,
>> + SAS, or iSCSI,
>> + - for non-SCSI hardware which speaks SCSI protocols, such as USB
>> + storage devices or the parallel port version of Iomega Zip drive,
>
>
> but not for CONFIG_BLK_DEV_UB
>
>
>> + - for non-SCSI hardware whose drivers translate from and to SCSI
>> + protocols, most notably all Serial ATA drivers, and Parallel ATA
>> + via the ATA configuration option.
>
>
> but not for CONFIG_BLK_DEV_IDE_SATA
Well, one could add a
You don't need it
- for x,
- for y.
bullet list.
...
> You expect all kconfig users to read and completely understand this?
I occasionally write documentation without the expectation that every
potential user will read and understand it.
> Although it's no longer required that the user sees the CONFIG_SCSI
> option at all since we can determine automaically when it's required
> and when not?
Maybe you can hide CONFIG_SCSI, but you still need to provide the above
information --- then under the sd, sr, st, sg options, which may
actually be the better places although it increases redundancy.
--
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists