From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: benh@kernel.crashing.org, anton@samba.org, rmk@arm.linux.org.uk,
mochel@osdl.org, willy@debian.org
Subject: Re: PCI stuff
Date: Fri, 13 Jun 2003 00:23:18 -0400 [thread overview]
Message-ID: <1055478198.4048.146.camel@cube> (raw)
> The new pci_domain_nr() is good for adding the PCI domain
> number to the /sys/devices/pciN/* names, but I think that's
> not the proper representation. It should really be
>
> /sys/devices/pci-domainN/pciN/*
>
> So we can pave the way for when we'll stop play bus number
> tricks and actually have overlapping PCI bus numbers between
> domains. (I don't plan to do that immediately because that
> would break userland & /proc/bus/pci backward compatiblity)
>
> What do you think ?
This should have been obvious to me last week:
/sys/devices/pciN/busM/devQ/fnP/*
N is the thingy number. (domain, segment, hose...)
It's important to get the interface right, even if
that means a bit of short-term trouble. We'll be
stuck with the interface, like it or not, for a
damn long time once 2.6.xx gets established.
reply other threads:[~2003-06-13 4:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1055478198.4048.146.camel@cube \
--to=albert@users.sf.net \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rmk@arm.linux.org.uk \
--cc=willy@debian.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.