From: Jeremy Kerr <jk@ozlabs.org>
To: Milton Miller <miltonm@bga.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 3/20] [powerpc] Remove linux,pci-domain properties
Date: Wed, 5 Jul 2006 09:22:18 +1000 [thread overview]
Message-ID: <200607050922.19779.jk@ozlabs.org> (raw)
In-Reply-To: <e53c7a64d7260d56983e22360cb5dd5a@bga.com>
Milton,
> Without looking at the mentioned utilities, DLPAR and PCI Hotplug get
> a location code, so I'm hoping that the pci slot name is identified
> by that. Is lsvpd scanning? Or does it scan sysfs first and
> /proc/device-tree secondarly?
Yes, lsvpd scans sysfs first, then uses devspec to refer to the device
tree. and AFAICT, the slot id can't be extracted from the location
code.
So you're saying that the linux,pci-domain property is still in use,
right? If so, I'll do up a patch to fix add_linux_pci_domain rather
than removing it.
Cheers,
Jeremy
next prev parent reply other threads:[~2006-07-04 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 7:55 [PATCH 3/20] [powerpc] Remove linux,pci-domain properties Milton Miller
2006-07-04 23:22 ` Jeremy Kerr [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-04 6:47 Jeremy Kerr
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=200607050922.19779.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=paulus@samba.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).