From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, willy@debian.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH] add legacy resources to sysfs
Date: Wed, 22 Dec 2004 16:34:37 +0000 [thread overview]
Message-ID: <1103733278.31693.83.camel@gaston> (raw)
In-Reply-To: <20041222160952.GB9358@kroah.com>
On Wed, 2004-12-22 at 08:09 -0800, Greg KH wrote:
> Hm, what do you mean by "instance"? My /sys/class/pci_bus has the
> individual pci busses:
> $ tree /sys/class/pci_bus/
> /sys/class/pci_bus/
> |-- 0000:00
> | |-- bridge -> ../../../devices/pci0000:00
> | `-- cpuaffinity
> |-- 0000:01
> | |-- bridge -> ../../../devices/pci0000:00/0000:00:01.0
> | `-- cpuaffinity
> `-- 0000:02
> |-- bridge -> ../../../devices/pci0000:00/0000:00:1e.0
> `-- cpuaffinity
>
>
> We already have the cpuaffinity stuff in there, why not more, pci bus
> specific things?
Oh, I misread. If it's in /sys/class/pci_bus/(instance)/file it's fine,
sorry, my fault.
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, willy@debian.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH] add legacy resources to sysfs
Date: Wed, 22 Dec 2004 17:34:37 +0100 [thread overview]
Message-ID: <1103733278.31693.83.camel@gaston> (raw)
In-Reply-To: <20041222160952.GB9358@kroah.com>
On Wed, 2004-12-22 at 08:09 -0800, Greg KH wrote:
> Hm, what do you mean by "instance"? My /sys/class/pci_bus has the
> individual pci busses:
> $ tree /sys/class/pci_bus/
> /sys/class/pci_bus/
> |-- 0000:00
> | |-- bridge -> ../../../devices/pci0000:00
> | `-- cpuaffinity
> |-- 0000:01
> | |-- bridge -> ../../../devices/pci0000:00/0000:00:01.0
> | `-- cpuaffinity
> `-- 0000:02
> |-- bridge -> ../../../devices/pci0000:00/0000:00:1e.0
> `-- cpuaffinity
>
>
> We already have the cpuaffinity stuff in there, why not more, pci bus
> specific things?
Oh, I misread. If it's in /sys/class/pci_bus/(instance)/file it's fine,
sorry, my fault.
Ben.
next prev parent reply other threads:[~2004-12-22 16:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 20:47 [PATCH] add legacy resources to sysfs Jesse Barnes
2004-12-21 20:47 ` Jesse Barnes
2004-12-21 21:28 ` Matthew Wilcox
2004-12-21 21:28 ` Matthew Wilcox
2004-12-21 21:44 ` Greg KH
2004-12-21 21:44 ` Greg KH
2004-12-21 21:49 ` Jesse Barnes
2004-12-21 21:49 ` Jesse Barnes
2004-12-21 21:46 ` Greg KH
2004-12-21 21:46 ` Greg KH
2004-12-21 22:05 ` Jesse Barnes
2004-12-21 22:05 ` Jesse Barnes
2004-12-21 23:42 ` Jesse Barnes
2004-12-22 0:05 ` Greg KH
2004-12-22 0:14 ` Jesse Barnes
2004-12-22 0:20 ` Greg KH
2004-12-22 8:38 ` Benjamin Herrenschmidt
2004-12-22 8:38 ` Benjamin Herrenschmidt
2004-12-22 16:09 ` Greg KH
2004-12-22 16:09 ` Greg KH
2004-12-22 16:34 ` Benjamin Herrenschmidt [this message]
2004-12-22 16:34 ` Benjamin Herrenschmidt
2004-12-22 16:58 ` Jesse Barnes
2004-12-22 16:58 ` Jesse Barnes
2004-12-22 18:31 ` Jesse Barnes
2004-12-22 18:31 ` Jesse Barnes
2004-12-22 21:07 ` Greg KH
2004-12-22 21:07 ` 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=1103733278.31693.83.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=bjorn.helgaas@hp.com \
--cc=greg@kroah.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.