public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Staging: only build the tree if we really want to
Date: Sat, 8 Nov 2008 10:30:44 -0800	[thread overview]
Message-ID: <20081108183044.GA16504@suse.de> (raw)
In-Reply-To: <4915B769.6090403@s5r6.in-berlin.de>

On Sat, Nov 08, 2008 at 04:59:37PM +0100, Stefan Richter wrote:
> Greg KH wrote:
> > --- a/drivers/staging/Kconfig
> > +++ b/drivers/staging/Kconfig
> > @@ -21,7 +21,23 @@ menuconfig STAGING
> >  
> >  	  If in doubt, say N here.
> >  
> > -if STAGING
> > +
> > +config STAGING_EXCLUDE_BUILD
> > +	bool "Exclude Staging drivers from being built"
> > +	default y
> > +	---help---
> ...
> > +if !STAGING_EXCLUDE_BUILD
> >  
> >  source "drivers/staging/et131x/Kconfig"
> >  
> > @@ -45,4 +61,4 @@ source "drivers/staging/at76_usb/Kconfig"
> >  
> >  source "drivers/staging/poch/Kconfig"
> >  
> > -endif # STAGING
> > +endif # !STAGING_EXCLUDE_BUILD
> 
> Which purpose is the STAGING kconfig variable serving after this?

Sitting there and looking pretty :)

> It controls the visibility of the menu, but switching it off won't
> switch off the staging drivers if they were previously enabled, would
> it?

Try it and look in wonder :)

If something affects the visibility of the menu for those config
options, it controls if those options can be enabled or not.

thanks,

greg k-h

  reply	other threads:[~2008-11-08 18:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08  5:45 [GIT PATCH] STAGING fixes for 2.6.28 Greg KH
2008-11-08  5:45 ` [PATCH 1/2] Staging: only build the tree if we really want to Greg KH
2008-11-08 15:59   ` Stefan Richter
2008-11-08 18:30     ` Greg KH [this message]
2008-11-08 19:31       ` Stefan Richter
2008-11-11  6:15         ` Greg KH
2008-11-08  5:45 ` [PATCH 2/2] Staging: make usbip depend on CONFIG_NET Greg KH

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=20081108183044.GA16504@suse.de \
    --to=gregkh@suse.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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