public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Latest paulus.git PCI broken on mpc8540?
Date: Sat, 17 Nov 2007 08:20:39 +1100	[thread overview]
Message-ID: <1195248039.28865.180.camel@pasglop> (raw)
In-Reply-To: <473E084B.4080703@anagramm.de>


> 
> I don't know much of the code, so, propably a stupid question:
> Can we avoid to do the initial resource allocation, when it's known to fail?
> 
> It seems to me like things are done twice here:
> 1. try
> 2. reallocate
> 3. retry

Well, we don't know it's going to fail until we try :-)

Ben.

  reply	other threads:[~2007-11-16 21:20 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
2007-11-16 21:14         ` Clemens Koller
2007-11-16 21:20           ` Benjamin Herrenschmidt [this message]
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=1195248039.28865.180.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=clemens.koller@anagramm.de \
    --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