From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, jeffrey.t.kirsher@intel.com
Subject: Re: linux-next: boot test failure (net tree)
Date: Wed, 17 Aug 2011 10:50:02 +1000 [thread overview]
Message-ID: <20110817105002.efebf85d08460ad99b14be8e@canb.auug.org.au> (raw)
In-Reply-To: <20110816.171525.639251389938336183.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
Hi Dave,
On Tue, 16 Aug 2011 17:15:25 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 17 Aug 2011 10:01:46 +1000
>
> > In particular, CONFIG_TIGON3 newly depends on
> > CONFIG_NET_VENDOR_BROADCOM which will no be selected when doing a
> > "make oldconfig" from a working config.
>
> When you type "make oldconfig" with an existing .config it prompts you
> for those vendor guards, giving you ample opportunity to say yes to
> them.
Which is a bit of a pain for automated systems. Ours does (essentially):
yes '' | make oldconfig
We really don't want to select every new config item that comes along.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-08-17 0:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 0:01 Stephen Rothwell
2011-08-17 0:15 ` David Miller
2011-08-17 0:50 ` Stephen Rothwell [this message]
2011-08-17 0:56 ` David Miller
2011-08-17 1:19 ` Ben Hutchings
2011-08-17 3:04 ` David Miller
2011-08-17 1:21 ` Stephen Rothwell
2011-08-17 3:05 ` David Miller
2011-08-18 5:22 ` Stephen Rothwell
2011-08-18 5:40 ` Jeff Kirsher
2011-08-18 5:53 ` David Miller
2011-08-22 1:30 ` Stephen Rothwell
2011-08-23 1:40 ` Stephen Rothwell
2011-08-23 1:41 ` Stephen Rothwell
2011-08-23 2:13 ` David Miller
2011-08-23 2:26 ` Jeff Kirsher
2011-08-23 3:50 ` Arnaud Lacombe
2011-08-23 4:02 ` David Miller
2011-08-23 8:29 ` Jeff Kirsher
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=20110817105002.efebf85d08460ad99b14be8e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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®