From: Matthew Dobson <colpatch@us.ibm.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Greg KH <greg@kroah.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Martin Bligh <mjbligh@us.ibm.com>
Subject: Re: [rfc][patch] driverfs multi-node(board) patch [2/2]
Date: Tue, 01 Oct 2002 11:44:19 -0700 [thread overview]
Message-ID: <3D99ED03.8040600@us.ibm.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210011125290.27710-100000@cherise.pdx.osdl.net
Patrick Mochel wrote:
> Matt,
>
> I have some comments about the structure of the code, but those will come
> in another email..
Cool... Any/all comments are definitely welcome...
>>[root@elm3b79 devices]# tree -d root/sys/
>>root/sys/
>>|-- node0
>>| `-- sys
>>| |-- cpu0
>>| |-- cpu1
>>| |-- cpu2
>>| |-- cpu3
>>| `-- memblk0
>>|-- node1
>>| `-- sys
>>| |-- cpu4
>>| |-- cpu5
>>| |-- cpu6
>>| |-- cpu7
>>| `-- memblk1
>>|-- pic0
>>`-- rtc0
>
>
> Shouldn't nodes (or, erm, boards) be added as children of the root?
Um, yes! I don't quite know how, though... I call sys_register_root()
for each of the nodes... That call seems to parent them under the
root/sys directory... How can I change that?
> Aren't all types of devices present on the various boards (PCI, etc)?
Yes... I have some patches that I'm working that will put PCI busses
and devices into the topology infrastructure (both in-kernel & via
driverfs). Again, this is just a first pass of what I'd like to see... ;)
Cheers!
-Matt
>
> -pat
>
>
next prev parent reply other threads:[~2002-10-01 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 1:00 [rfc][patch] driverfs multi-node(board) patch [1/2] Matthew Dobson
2002-10-01 1:03 ` [rfc][patch] driverfs multi-node(board) patch [2/2] Matthew Dobson
2002-10-01 5:41 ` Greg KH
2002-10-01 18:19 ` Matthew Dobson
2002-10-01 18:28 ` Patrick Mochel
2002-10-01 18:44 ` Matthew Dobson [this message]
2002-10-01 18:54 ` Patrick Mochel
2002-10-03 21:34 ` Patrick Mochel
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=3D99ED03.8040600@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjbligh@us.ibm.com \
--cc=mochel@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 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).