[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110817112110.ec81ef078204bf4a02049a66@canb.auug.org.au>
Date: Wed, 17 Aug 2011 11:21:10 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: David Miller <davem@...emloft.net>
Cc: netdev@...r.kernel.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, jeffrey.t.kirsher@...el.com
Subject: Re: linux-next: boot test failure (net tree)
Hi Dave,
On Tue, 16 Aug 2011 17:56:57 -0700 (PDT) David Miller <davem@...emloft.net> wrote:
>
> From: Stephen Rothwell <sfr@...b.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.
Notice the '' that just is the same as typing return to every prompt. In
the case of these new gueards, that means 'n'. This will be the same
with "make silentoldconfig".
> This happens on other occaisions, I see new group guards all
> the time when I resync my net and net-next trees with Linus.
"All the time"? really?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists