Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764118AbYBTA3g (ORCPT ); Tue, 19 Feb 2008 19:29:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758863AbYBTA31 (ORCPT ); Tue, 19 Feb 2008 19:29:27 -0500 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:57918 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1758093AbYBTA30 (ORCPT ); Tue, 19 Feb 2008 19:29:26 -0500 Date: Tue, 19 Feb 2008 16:30:03 -0800 (PST) Message-Id: <20080219.163003.152862383.davem@davemloft.net> To: galak@kernel.crashing.org Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org Subject: Re: [PATCH v2][POWERPC] Fix initial lmb add region with a non-zero base From: David Miller In-Reply-To: References: X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1052 Lines: 29 From: Kumar Gala Date: Tue, 19 Feb 2008 13:51:37 -0600 (CST) > If we add to an empty lmb region with a non-zero base we will not coalesce > the number of regions down to one. This causes problems on ppc32 for the > memory region as its assumed to only have one region. > > We can fix this easily by causing the initial add to replace the dummy > region. > > Signed-off-by: Kumar Gala > --- > > Fix a bug the initial patch introduced if we have a region that gets added > at the beginning of the list we wouldn't actually add it. > > Dave can you replace the patch in you tree with this one. I think my tree has already or will soon be pulled in so I don't want to rebase it. Why don't you simply send me the relative bug fix instead? Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/