From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 5B4D72C02AD for ; Tue, 24 Jul 2012 08:26:45 +1000 (EST) Message-ID: <1343082371.2957.39.camel@pasglop> Subject: Re: next/mmotm unbootable on G5: irqdomain From: Benjamin Herrenschmidt To: Grant Likely Date: Tue, 24 Jul 2012 08:26:11 +1000 In-Reply-To: References: <1343011543.2957.2.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: Stephen Rothwell , Hugh Dickins , linux-kernel@vger.kernel.org, Milton Miller , Paul Mundt , Rob Herring , Andrew Morton , linuxppc-dev@lists.ozlabs.org, Thomas Gleixner List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2012-07-23 at 01:59 -0600, Grant Likely wrote: > My tree must be rebased to eliminate bisect breakage. The existing > commits in my tree have the breakage, and fiddling with the merge > order doesn't affect that. I don't want to rebase though. The safest > approach (smallest window of breakage) is to apply that fix onto my > irqdomain tree. With your other breakage on pseries I'm thinking rebasing might be the only option... Cheers, Ben.