From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, 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 02:19:12 +0100 [thread overview]
Message-ID: <1313543952.2981.132.camel@deadeye> (raw)
In-Reply-To: <20110816.175657.1688139393736610845.davem@davemloft.net>
On Tue, 2011-08-16 at 17:56 -0700, David Miller wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 17 Aug 2011 10:50:02 +1000
>
> > 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.
>
> If you're indeed piping "yes" output to "make oldconfig" on an
> existing config, it would select the new guards for you.
[....]
If you were to use just "yes", then of course it would. But since there
is no explicit default, "yes ''" will deselect them.
Maybe these guards should have "default y"?
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-08-17 1:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 0:01 linux-next: boot test failure (net tree) Stephen Rothwell
2011-08-17 0:15 ` David Miller
2011-08-17 0:50 ` Stephen Rothwell
2011-08-17 0:56 ` David Miller
2011-08-17 1:19 ` Ben Hutchings [this message]
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=1313543952.2981.132.camel@deadeye \
--to=bhutchings@solarflare.com \
--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 \
--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).