linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Latest paulus.git PCI broken on mpc8540?
Date: Sat, 17 Nov 2007 08:09:17 +1100	[thread overview]
Message-ID: <1195247357.28865.178.camel@pasglop> (raw)
In-Reply-To: <A4E1A594-5A31-4EFE-B4F9-E4B24F9207F7@kernel.crashing.org>


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.

  reply	other threads:[~2007-11-16 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 17:20 Latest paulus.git PCI broken on mpc8540? Clemens Koller
2007-11-16  4:37 ` Kumar Gala
2007-11-16  5:35   ` Benjamin Herrenschmidt
2007-11-16 19:18     ` Kumar Gala
2007-11-16 21:09       ` Benjamin Herrenschmidt [this message]
2007-11-16 21:14         ` Clemens Koller
2007-11-16 21:20           ` Benjamin Herrenschmidt
2007-11-16 21:45         ` Kumar Gala

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1195247357.28865.178.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).