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 ESMTP id E51DBDDDE6 for ; Sat, 17 Nov 2007 08:09:27 +1100 (EST) Subject: Re: Latest paulus.git PCI broken on mpc8540? From: Benjamin Herrenschmidt To: Kumar Gala In-Reply-To: References: <473C7FCC.7050307@anagramm.de> <4E0EFED3-8697-4768-9D89-A2443AEC82A5@kernel.crashing.org> <1195191333.28865.140.camel@pasglop> Content-Type: text/plain Date: Sat, 17 Nov 2007 08:09:17 +1100 Message-Id: <1195247357.28865.178.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-embedded@ozlabs.org Reply-To: benh@kernel.crashing.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2007-11-16 at 13:18 -0600, Kumar Gala wrote: > > > Well, for one the generic pci code will complain if its not able to > allocate the resource which is the true failure. > > I'm thinking maybe we just make these pr_debug() instead of standard > printk? I was thinking about changing the message to "cannot allocate initial resource, will reallocate" or something like that. That is, make it clear it's non fatal. Ben.