Re: [PATCH][RFC] Restructure Device Driver menu entries

["Robert P. J. Day" <rpjday@mindspring.com>]

On Wed, 6 Dec 2006, Randy Dunlap wrote:

> On Wed, 6 Dec 2006 09:33:46 -0500 (EST) Robert P. J. Day wrote:
>
> >
> >   This is a *proposed* restructuring of the DD menu so that one can
> > see and select/de-select entire submenus without having to enter each
> > submenu.    It's also immediately obvious visually which submenus are
> > currently active.
> >
> >   Based on Randy Dunlap's earlier suggestion, it uses the kbuild
> > "menuconfig" feature.  I changed only those sub-entries that matched
> > an obvious pattern (that is, selectable in their entirety).  If there
> > was *anything* slightly different about that sub-entry, I left it
> > alone.  (That doesn't mean that those sub-entries can't be similarly
> > tweaked with a minimum of effort, I was just keeping it simple for
> > now.)
> >
> >   Finally, if this structure is used, there's still a good deal of
> > cleanup that can be done on each Kconfig file.  For example, if most
> > of the mtd Kconfig file is now surrounded by
>
> The FUSION part has a dependency that I'll leave for you:
>
> Warning! Found recursive dependency: FUSION FUSION_SPI FUSION
>
> reported by any "make *config".

ah, quite right, i missed that.  that's because the fusion Kconfig
file starts with:

menu "Fusion MPT device support"

config FUSION
	bool
	default n

config FUSION_SPI
	tristate "Fusion MPT ScsiHost drivers for SPI"
	depends on PCI && SCSI   <-- not dependent on FUSION
	select FUSION
	select SCSI_SPI_ATTRS
	...

  for now, then, i'm just going to remove the FUSION menu change from
the upcoming patch and decide what to do about it later.  as i
mentioned, i wanted this first patch to restructure entries that
required nothing more than the obvious rewrite.  upcoming patch ...
uh, upcoming shortly.

rday
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/