From: CaT <cat@zip.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: promise controller resource alloc problems with ~2.6.8
Date: Fri, 1 Oct 2004 20:30:32 +1000 [thread overview]
Message-ID: <20041001103032.GA1049@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0409301646040.2403@ppc970.osdl.org>
On Thu, Sep 30, 2004 at 04:56:21PM -0700, Linus Torvalds wrote:
> Now, the reason for using "insert_resource()" in arch/i386/pci/i386.c
> should go away with Shaohua Li's patch, so I'd love to hear if applying
> Li's patch _and_ making the "insert_resource()" be a "request_resource()"
> fixes the problem for you.
You meant this, right?
if (!pr || insert_resource(pr, r) < 0)
printk(KERN_ERR "PCI: Cannot allocate resource region %d of bridge %s\n", idx, pci_name(dev));
If so then the patch + the above did not work. :/
> Greg, we kind of left the ACPI resource management breakage pending, and
> clearly we need some resolution. Comments?
BTW. I just realised (and I apologise for not doing so earlier) that I'm
not using ACPI on this box.
--
Red herrings strewn hither and yon.
next prev parent reply other threads:[~2004-10-01 10:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 8:45 promise controller resource alloc problems with ~2.6.8 CaT
2004-09-30 23:03 ` CaT
2004-09-30 23:21 ` Linus Torvalds
2004-09-30 23:30 ` CaT
2004-09-30 23:56 ` Linus Torvalds
2004-10-01 0:14 ` Greg KH
2004-10-01 1:23 ` CaT
2004-10-01 10:30 ` CaT [this message]
2004-10-01 14:34 ` Linus Torvalds
2004-10-02 4:57 ` CaT
2004-10-02 19:17 ` Linus Torvalds
2004-10-10 2:19 ` CaT
2004-10-10 3:15 ` Linus Torvalds
2004-10-10 3:30 ` Linus Torvalds
2004-10-10 4:51 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-10-10 5:28 Li, Shaohua
2004-10-10 17:00 ` Linus Torvalds
2004-10-12 12:52 ` CaT
2004-10-12 16:03 ` Greg KH
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=20041001103032.GA1049@zip.com.au \
--to=cat@zip.com.au \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.