From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: linux-next: sound tree build failure Date: Fri, 14 Nov 2008 08:14:04 +0100 Message-ID: References: <20081114145630.31f312ce.sfr@canb.auug.org.au> <20081114175856.2ab38113.sfr@canb.auug.org.au> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-2022-JP Return-path: Received: from ns2.suse.de ([195.135.220.15]:42503 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750799AbYKNHOG (ORCPT ); Fri, 14 Nov 2008 02:14:06 -0500 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org At Fri, 14 Nov 2008 08:07:44 +0100, 私 wrote: > > At Fri, 14 Nov 2008 17:58:56 +1100, > Stephen Rothwell wrote: > > > > Hi Takashi, > > > > On Fri, 14 Nov 2008 07:32:23 +0100 Takashi Iwai wrote: > > > > > > > That identifier does not exist anywhere else in my tree. It was removed > > > > by commit 621a0d5207c18012cb39932f2d9830a11a6cb03d ("hrtimer: clean up > > > > unused callback modes") which is now in Linus' tree (as of yesterday). > > > > > > I had to rebase the tree yesterday, but the code there is identical with > > > the older versions. So, if it failed there, it must be a change of > > > hrtimer side. > > > > > > I'll check tip tree... > > > > That commit entered Linus' tree after you rebased your tree but before I > > fetched it this morning. You could fix things by merging Linus' tree and > > doing the fix in the merge commit rather than rebasing. > > To defense myself: the reason of the rebase is irrelevant with this > build error. It's just a sad coincident. Well, what I wanted to say is that the rebase on my tree is fairly rare (IIRC, it was the first time after 2.6.28-rc1), and this build error would occur regardless of rebase or not... Sigh. Takashi