From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - udevinfo with device chain walk
Date: Fri, 23 Jan 2004 20:43:12 +0000 [thread overview]
Message-ID: <20040123204312.GE23959@kroah.com> (raw)
In-Reply-To: <20040123013054.GA2437@vrfy.org>
On Fri, Jan 23, 2004 at 10:24:44AM +0500, Ananth N Mavinakayanahalli wrote:
> On Thu, Jan 22, 2004 at 07:03:44PM -0800, Greg KH wrote:
> >
> > Ananth, I think this is pointing out a bug in libsysfs, see below:
> >
> > On Fri, Jan 23, 2004 at 02:30:54AM +0100, Kay Sievers wrote:
> > >
> > > looking at the device chain at '/sys/devices/pci0000:00':
> > > BUS=""
> > > ID="pci0000:00"
> > > SYSFS_detach_state="0"
> >
> > This device should show up on with BUS="pci", right?
>
> Right.. it does not show up here since the device pci0000:00 does not have
> a link under the "bus" subsystem. This is presently the case for all "root"
> devices (entries under /sys/devices). Will fix this.
Hm, looks like libsysfs is correct, as that device does not show up in
the sys/bus/pci/devices directory. I think I have patch in my kernel
tree to help fix that up...
Nevermind, sorry for the false alarm.
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-01-23 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 1:30 [PATCH] udev - udevinfo with device chain walk Kay Sievers
2004-01-23 3:01 ` Greg KH
2004-01-23 3:03 ` Greg KH
2004-01-23 4:53 ` Ananth N Mavinakayanahalli
2004-01-23 20:43 ` Greg KH [this message]
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=20040123204312.GE23959@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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.