From: Greg KH <greg@kroah.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Harvey Harrison <harvey.harrison@gmail.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-next@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: linux-next: v4l-dvb tree build failure
Date: Fri, 7 Nov 2008 21:08:53 -0800 [thread overview]
Message-ID: <20081108050853.GA10926@kroah.com> (raw)
In-Reply-To: <20081108043816.GB10465@kroah.com>
On Fri, Nov 07, 2008 at 08:38:16PM -0800, Greg KH wrote:
> On Sat, Nov 08, 2008 at 04:05:35AM +0100, Sam Ravnborg wrote:
> > On Sat, Nov 08, 2008 at 09:59:50AM +1100, Stephen Rothwell wrote:
> > > Hi Harvey,
> > >
> > > On Fri, 07 Nov 2008 09:43:57 -0800 Harvey Harrison <harvey.harrison@gmail.com> wrote:
> > > >
> > > > Is it really fair to drop the v4l tree when it was -staging that broke? I'd humbly
> > > > suggest that staging be weighted somewhat lower than the other trees.
> > >
> > > There is no staging tree in linux-next, that driver is in Linus' tree. I
> > > agree that if there was a staging tree, it would be much lower priority.
> > >
> > > Maybe we need some way to exclude the staging directory from
> > > all{yes,mod}config builds ...
> >
> > That is simple to do. Something like:
> >
> > config STAGING_EXCLUDE_BUILD
> > bool "Exclude Staging from the build"
> >
> >
> > And test for this in the Staging Makefile
> >
> > When this is set to 'y' then we will not build
> > the staging tree.
>
> While that would work, it does seem odd to be asked two things:
> "Staging drivers (y/N)"
> if Y is chosen, they then get asked:
> "Exclude Staging from the build? (Y/n)"
>
> It's like, "are you sure you really want to build this part of the
> tree?" If that would make people's lives easier, I have no objection to
> it, it's just kind of funny :)
>
> Stephen, what do you think?
In thinking about it a bit more, I kind of like it. So here's the patch
I just added to the staging tree:
---
drivers/staging/Kconfig | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
--- 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---
+ Are you sure you really want to build the staging drivers?
+ They taint your kernel, don't live up to the normal Linux
+ kernel quality standards, are a bit crufty around the edges,
+ and might go off and kick your dog when you aren't paying
+ attention.
+
+ Say N here to be able to select and build the Staging drivers.
+ This option is primarily here to prevent them from being built
+ when selecting 'make allyesconfg' and 'make allmodconfig' so
+ don't be all that put off, your dog will be just fine.
+
+if !STAGING_EXCLUDE_BUILD
source "drivers/staging/et131x/Kconfig"
@@ -59,4 +75,4 @@ source "drivers/staging/comedi/Kconfig"
source "drivers/staging/asus_oled/Kconfig"
-endif # STAGING
+endif # !STAGING_EXCLUDE_BUILD
next prev parent reply other threads:[~2008-11-08 5:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 3:30 linux-next: v4l-dvb tree build failure Stephen Rothwell
2008-11-07 17:43 ` Harvey Harrison
2008-11-07 18:41 ` Greg KH
2008-11-07 23:02 ` Stephen Rothwell
2008-11-12 0:54 ` Mauro Carvalho Chehab
2008-11-12 22:45 ` Greg KH
2008-11-07 22:59 ` Stephen Rothwell
2008-11-07 23:06 ` Greg KH
2008-11-08 3:05 ` Sam Ravnborg
2008-11-08 4:38 ` Greg KH
2008-11-08 5:08 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 6:59 Stephen Rothwell
2010-01-27 23:24 ` Andy Walls
2010-01-28 1:54 ` Mauro Carvalho Chehab
2010-01-28 5:24 ` Stephen Rothwell
2009-04-07 0:58 Stephen Rothwell
2009-04-07 1:20 ` Mauro Carvalho Chehab
2009-04-07 4:47 ` Stephen Rothwell
2009-03-27 0:40 Stephen Rothwell
2009-03-27 11:28 ` Mauro Carvalho Chehab
2009-03-27 14:03 ` Stephen Rothwell
2009-03-05 0:35 Stephen Rothwell
2009-03-05 21:51 ` Mauro Carvalho Chehab
2009-03-06 0:05 ` Stephen Rothwell
2009-03-06 1:15 ` Mauro Carvalho Chehab
2009-03-02 0:05 Stephen Rothwell
2009-03-02 0:08 ` Michael Krufky
2009-03-02 0:30 ` Stephen Rothwell
2009-03-02 2:52 ` Mauro Carvalho Chehab
2008-12-08 2:07 Stephen Rothwell
2008-12-01 23:37 Stephen Rothwell
2008-12-02 10:03 ` Mauro Carvalho Chehab
2008-12-02 22:23 ` Stephen Rothwell
2008-12-03 22:48 ` Mauro Carvalho Chehab
2008-12-03 0:08 ` Stephen Rothwell
2008-12-03 22:49 ` Mauro Carvalho Chehab
2008-11-25 4:41 Stephen Rothwell
2008-10-29 2:20 Stephen Rothwell
2008-10-29 12:26 ` Andreas Oberritter
2008-11-03 1:52 ` Stephen Rothwell
2008-11-05 1:57 ` Stephen Rothwell
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=20081108050853.GA10926@kroah.com \
--to=greg@kroah.com \
--cc=harvey.harrison@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.