From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757490AbZBKPGN (ORCPT ); Wed, 11 Feb 2009 10:06:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757072AbZBKPFy (ORCPT ); Wed, 11 Feb 2009 10:05:54 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:38213 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756492AbZBKPFx (ORCPT ); Wed, 11 Feb 2009 10:05:53 -0500 Date: Wed, 11 Feb 2009 16:05:36 +0100 From: Ingo Molnar To: Dean Nelson Cc: Andrew Morton , Tejun Heo , Tony Luck , linux-ia64 , linux-next , LKML Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Message-ID: <20090211150536.GE10525@elte.hu> References: <20090209162520.GA4882@sgi.com> <20090210132555.be1c1462.akpm@linux-foundation.org> <20090211150103.GA15814@sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090211150103.GA15814@sgi.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Dean Nelson wrote: > On Tue, Feb 10, 2009 at 01:25:55PM -0800, Andrew Morton wrote: > > On Mon, 9 Feb 2009 10:25:20 -0600 > > Dean Nelson wrote: > > > > > Fix the ia64 build error that occurs in the linux-next tree by introducing > > > an ia64 version of uv.h. Additionally, clean up the usage of is_uv_system(). > > > > Would I be correct in believing that this repairs (and should be folded > > into) > > > > commit 5b221278d61e3907a5e4104a844b63bc8bb3d43a > > Author: Ingo Molnar > > Date: Wed Jan 21 11:30:07 2009 +0100 > > > > x86: uv cleanup, build fix #2 > > > > ? > > > > (it looks like 5b221278d61e3907a5e4104a844b63bc8bb3d43a should be > > folded into something else, too. What hath we wrought?) > > Yes, it does fix an issue introduced by: > > commit: bdbcdd48883940bbd8d17eb01172d58a261a413a > author: Tejun Heo > date: Wed, 21 Jan 2009 08:26:06 +0000 > > x86: uv cleanup > > which the commit you mention above attempted to fix. > > I'll leave it to you and Ingo to determine whether my patch should be > folded into Ingo's or Tejun's patch. > > Ingo, I see that you've applied my patch to your tip tree. What are > your thoughts on Andrew's question? 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. Ingo