From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Rusty Russell <rusty@rustcorp.com.au>,
gregkh@suse.de, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 23
Date: Mon, 23 Nov 2009 15:37:46 -0800 [thread overview]
Message-ID: <4B0B1CCA.7070500@oracle.com> (raw)
In-Reply-To: <20091124103641.abd7bd6b.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Randy,
>
> On Mon, 23 Nov 2009 15:04:39 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> I decided to check on linux-next (only checked x86_64 allmodconfig),
>> and viola:
>>
>> CONFIG_STAGING=y
>> CONFIG_STAGING_EXCLUDE_BUILD=y
>>
>> That is just too helpful. :(
>
> The Kconfig was deliberately done so that the all{no,yes,mod}config
> builds don't build the staging stuff. You need to explictly ask for it.
> Otherwise I would spend all my time reporting/fixing errors and warnings
> in linux-next.
>
no, you should just drop it after one build error.
--
~Randy
next prev parent reply other threads:[~2009-11-23 23:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 7:52 linux-next: Tree for November 23 Stephen Rothwell
2009-11-23 13:04 ` Michal Simek
2009-11-23 13:19 ` Ralf Baechle
2009-11-23 13:43 ` Michal Simek
2009-11-23 19:15 ` Randy Dunlap
2009-11-23 22:54 ` Rusty Russell
2009-11-23 23:04 ` Randy Dunlap
2009-11-23 23:36 ` Stephen Rothwell
2009-11-23 23:37 ` Randy Dunlap [this message]
2009-11-23 23:43 ` Greg KH
2009-11-23 23:44 ` Randy Dunlap
2009-11-23 23:33 ` Stephen Rothwell
2009-11-23 23:34 ` Randy Dunlap
2009-11-23 23:39 ` Greg KH
2009-11-23 23:43 ` Randy Dunlap
2009-11-23 23:38 ` Greg KH
2009-11-23 23:42 ` Randy Dunlap
2009-11-24 2:34 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-11-23 3:06 Stephen Rothwell
2010-11-23 15:43 ` Zimny Lech
2010-11-23 17:15 ` Randy Dunlap
2010-11-23 19:03 ` Zimny Lech
2010-11-23 19:04 ` Zimny Lech
2010-11-23 15:45 ` Zimny Lech
2010-11-23 16:32 ` Anca Emanuel
2010-11-23 17:11 ` Anca Emanuel
2010-11-25 5:58 ` Stephen Rothwell
2010-11-24 9:24 ` Zimny Lech
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=4B0B1CCA.7070500@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 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).