LKML Archive on
help / color / mirror / Atom feed
From: "Robert P. J. Day" <>
To: Randy Dunlap <>
Cc: Linux kernel mailing list <>
Subject: Re: [PATCH][RFC] Restructure Device Driver menu entries
Date: Thu, 7 Dec 2006 03:49:27 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0612070345440.6261@localhost.localdomain> (raw)
In-Reply-To: <>

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
	default n

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

  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.


  reply	other threads:[~2006-12-07  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 14:33 Robert P. J. Day
2006-12-06 19:54 ` Randy Dunlap
2006-12-06 20:12 ` Randy Dunlap
2006-12-07  8:49   ` Robert P. J. Day [this message]
2006-12-06 21:04 ` Jan Engelhardt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0612070345440.6261@localhost.localdomain \ \ \ \
    --subject='Re: [PATCH][RFC] Restructure Device Driver menu entries' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).