From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Hutchings Subject: Re: linux-next: boot test failure (net tree) Date: Wed, 17 Aug 2011 02:19:12 +0100 Message-ID: <1313543952.2981.132.camel@deadeye> References: <20110817100146.3b557cf815a5a2ae09bc09a7@canb.auug.org.au> <20110816.171525.639251389938336183.davem@davemloft.net> <20110817105002.efebf85d08460ad99b14be8e@canb.auug.org.au> <20110816.175657.1688139393736610845.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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 To: David Miller Return-path: In-Reply-To: <20110816.175657.1688139393736610845.davem@davemloft.net> Sender: linux-next-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, 2011-08-16 at 17:56 -0700, David Miller wrote: > From: Stephen Rothwell > 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.