From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: linux-next: origin tree build failure Date: Sat, 13 Jun 2009 00:19:58 +1000 Message-ID: <1244816398.7172.172.camel@pasglop> References: <20090612102427.32582baa.sfr@canb.auug.org.au> <1244768406.7172.1.camel@pasglop> <20090612092054.GB32052@elte.hu> <1244799197.7172.106.camel@pasglop> <20090612125335.GH31845@elte.hu> <1244812224.7172.146.camel@pasglop> <20090612134428.GC32105@elte.hu> <1244814976.7172.164.camel@pasglop> <20090612140730.GJ32105@elte.hu> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from gate.crashing.org ([63.228.1.57]:57812 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753325AbZFLOUc (ORCPT ); Fri, 12 Jun 2009 10:20:32 -0400 In-Reply-To: <20090612140730.GJ32105@elte.hu> Sender: linux-next-owner@vger.kernel.org List-ID: To: Ingo Molnar Cc: Stephen Rothwell , Linus , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, paulus@samba.org, ppc-dev > Uhm, the bug you are making a big deal of would have been found and > fixed by Paulus a few hours after any such mail - and probably by me > too as i do daily cross builds to Power. > > So yes, we had a bug, but any extra linux-next hoops would not have > prevented it: i could still have messed up by getting lured by that > nice piece of Power7 hardware enablement patch on the last day ;-) > > So the bug was my fault for being too fast-and-loose with that > particular patch, creating a ~5-commits-hop build breakage bisection > window on Power. > > Now that i'm sufficiently chastised, can we now move on please? :) Sure we can :-) My point is, get a break before you merge upstream :-) Cheers, Ben.