From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dean Nelson Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Date: Wed, 11 Feb 2009 13:33:19 -0600 Message-ID: <20090211193319.GA21987@sgi.com> References: <20090209162520.GA4882@sgi.com> <20090210132555.be1c1462.akpm@linux-foundation.org> <20090211150103.GA15814@sgi.com> <20090211150536.GE10525@elte.hu> <57C9024A16AD2D4C97DC78E552063EA361689D7D@orsmsx505.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from relay1.sgi.com ([192.48.179.29]:34309 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756106AbZBKTdV (ORCPT ); Wed, 11 Feb 2009 14:33:21 -0500 Content-Disposition: inline In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA361689D7D@orsmsx505.amr.corp.intel.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: "Luck, Tony" Cc: Ingo Molnar , Andrew Morton , Tejun Heo , linux-ia64 , linux-next , LKML On Wed, Feb 11, 2009 at 10:58:19AM -0800, Luck, Tony wrote: > > What question was that? Folding back across that distance is not possible > > in a Git workflow. I do regular cross-builds - the build bug did not trigger > > with the ia64 defconfig. > > I'm confused by this, as it definitely triggered for me. Perhaps > my build scripts do things a bit differently. Essentially I do: > > $ for c in `ls arch/ia64/configs` > > do > > cp arch/ia64/configs/$i .config > > yes '' | make oldconfig > > make > > done > > Which takes the default answer for any new questions that crop > up. This enabled the GRU driver in the case of the generic_defconfig, > and so the build failed because of the lack of asm/uv.h It always triggers for me as well. I also use generic_defconfig and request the default for any NEW questions.