From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ishizaki Kou <kou.ishizaki@toshiba.co.jp>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 14/16] Resource assignments for PCI devices on Celleb
Date: Thu, 16 Nov 2006 10:56:36 +1100 [thread overview]
Message-ID: <1163634996.5940.293.camel@localhost.localdomain> (raw)
In-Reply-To: <200611150958.kAF9wXTQ011153@toshiba.co.jp>
On Wed, 2006-11-15 at 18:58 +0900, Ishizaki Kou wrote:
> Celleb has multiple PCI buses. Devices on some of those PCI buses require to
> assign resources by Linux.
> This patch is for such buses not to claim resources, because claimed resource
> does not become a target for resource assign.
I do not fully understand why you need that. You should be able to let
the PCI code claim all resources wether they are on real PCI or not.
Ben.
next prev parent reply other threads:[~2006-11-15 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 9:58 [PATCH 14/16] Resource assignments for PCI devices on Celleb Ishizaki Kou
2006-11-15 23:56 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-17 10:14 Ishizaki Kou
2006-11-17 22:14 ` Benjamin Herrenschmidt
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=1163634996.5940.293.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=kou.ishizaki@toshiba.co.jp \
--cc=linuxppc-dev@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).