From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI slots
Date: Tue, 06 Nov 2007 22:13:10 +0000 [thread overview]
Message-ID: <20071106221310.GA22999@kroah.com> (raw)
In-Reply-To: <20071106174509.GP4415@austin.ibm.com>
On Tue, Nov 06, 2007 at 11:03:46AM -0700, Matthew Wilcox wrote:
> On Tue, Nov 06, 2007 at 11:45:10AM -0600, Linas Vepstas wrote:
> > Hi,
> >
> > Cross-posting to the udev mailing list.
>
> I was actually thinking that linux-scsi would be the more appropriate
> list for discussing the presentation of scsi bay information. But maybe
> the udev list is the right place to hash this out first.
>
> > I admit I don't quite understand udev. I do note that they have
> > managed to do the things they do without having had to deal
> > with physical location codes just yet. But perhaps they're
> > interested, or have some commentary? I am cross-posting
> > the long unedited message there, to provide some background
> > to the discussion.
>
> It might be worth also including a link to the original message:
>
> http://marc.info/?l=linux-pci&m\x119432330418980&w=2
>
> and to let the udev people know that we already have a /sys/bus/pci/slots,
> but it's only populated for slots which have a hotplug driver currently.
> I was assuming that knowledge on the part of linux-pci folks, but the
> udev people might not know about it.
Heh, as the one of the udev "people" is the same person who added that
sysfs file to the tree, I think we might already know about this :)
Anyway, udev deals with device nodes, which pci slots do not really
matter for, so I doubt udev will need to handle anything at all here.
thanks,
greg k-h
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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:[~2007-11-06 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 17:45 PCI slots Linas Vepstas
2007-11-06 18:03 ` Matthew Wilcox
2007-11-06 22:13 ` 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=20071106221310.GA22999@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 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).