Cc: Sam Ravnborg <sam@...>, James Bottomley <james.bottomley@...>, <linux-scsi@...>, Jeff Garzik <jeff@...>, Andi Kleen <andi@...>, Folkert van Heusden <folkert@...>, <linux-kernel@...>
On Fri, Sep 14, 2007 at 10:01:18PM +0200, Stefan Richter wrote:
Nearly right. ;-)
There are a few architectures not (yet) using drivers/Kconfig.
This way the order is wrong:
There should first be the lowlevel SCSI, SATA, USB etc. drivers, these
drivers should select CONFIG_SCSI, and then the menu offering support
for disk, CD,...
What is "storage support"?
SATA?
PATA?
USB mass storage?
MMC?
MTD?
Whether or not a driver uses the SCSI layer is an implementation detail
(it even differs for the two USB mass storage implementations and the
two PATA implementations in the kernel) the user shouldn't have to know
about.
I don't see any reason why CONFIG_SCSI should have to stay user-visible
at all after your patch.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-