mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild : Make Fusion MPT selectable from "Device drivers" menu
Date: Thu, 7 Dec 2006 08:43:07 -0800	[thread overview]
Message-ID: <20061207084307.7e6de9ec.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612070651560.17882@localhost.localdomain>

On Thu, 7 Dec 2006 06:59:52 -0500 (EST) Robert P. J. Day wrote:

> 
>   Rewrite the Fusion MPT Kconfig file so that all of MPT functionality
> is entirely selectable from "Device drivers."
> 
> Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>

Acked-by: Randy Dunlap <randy.dunlap@oracle.com>

but I think that you should cc: the FUSION email addresses
that are listed in the MAINTAINERS file...


> ---
> 
>   The original Kconfig file seems to have an odd structure, as you can
> see from the first part of the file:
> 
> ========================================================
> menu "Fusion MPT device support"
> 
> config FUSION
>         bool
>         default n
> 
> config FUSION_SPI
>         tristate "Fusion MPT ScsiHost drivers for SPI"
>         depends on PCI && SCSI
>         select FUSION
>         select SCSI_SPI_ATTRS
>         ...
> ========================================================
> 
>   note how the majority of entries in that file don't directly
> *depend* on FUSION.  instead, they depend on *external* config
> variables, and *select* FUSION, and this is not the only place i've
> noticed that kind of dependency wording.
> 
>   is that a regular feature?  having that structure certainly makes it
> slightly more difficult to rewrite the menu entries, and it's not
> clear there's any obvious advantage to doing it that way.
> 
> 
> diff --git a/drivers/message/fusion/Kconfig b/drivers/message/fusion/Kconfig
> index ea31d84..b2da14d 100644
> --- a/drivers/message/fusion/Kconfig
> +++ b/drivers/message/fusion/Kconfig
> @@ -1,14 +1,12 @@
> -
> -menu "Fusion MPT device support"
> -
> -config FUSION
> -	bool
> +menuconfig FUSION
> +	bool "Fusion MPT device support"
>  	default n
> 
> +if FUSION
> +
>  config FUSION_SPI
>  	tristate "Fusion MPT ScsiHost drivers for SPI"
>  	depends on PCI && SCSI
> -	select FUSION
>  	select SCSI_SPI_ATTRS
>  	---help---
>  	  SCSI HOST support for a parallel SCSI host adapters.
> @@ -23,7 +21,6 @@ config FUSION_SPI
>  config FUSION_FC
>  	tristate "Fusion MPT ScsiHost drivers for FC"
>  	depends on PCI && SCSI
> -	select FUSION
>  	select SCSI_FC_ATTRS
>  	---help---
>  	  SCSI HOST support for a Fiber Channel host adapters.
> @@ -40,7 +37,6 @@ config FUSION_FC
>  config FUSION_SAS
>  	tristate "Fusion MPT ScsiHost drivers for SAS"
>  	depends on PCI && SCSI
> - 	select FUSION
>  	select SCSI_SAS_ATTRS
>  	---help---
>  	  SCSI HOST support for a SAS host adapters.
> @@ -100,4 +96,4 @@ config FUSION_LAN
> 
>  	  If unsure whether you really want or need this, say N.
> 
> -endmenu
> +endif
> -


---
~Randy

      reply	other threads:[~2006-12-07 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 11:59 Robert P. J. Day
2006-12-07 16:43 ` Randy Dunlap [this message]

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=20061207084307.7e6de9ec.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /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®