From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [PATCH 4/4] ACPI PCI slot detection driver Date: Fri, 29 Feb 2008 21:25:42 -0800 Message-ID: <20080301052542.GD19353@suse.de> References: <20080229002341.GA21420@ldl.fc.hp.com> <20080229002938.GE21420@ldl.fc.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cantor2.suse.de ([195.135.220.15]:48691 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753731AbYCAFVT (ORCPT ); Sat, 1 Mar 2008 00:21:19 -0500 Content-Disposition: inline In-Reply-To: <20080229002938.GE21420@ldl.fc.hp.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Alex Chiang , Gary Hade , kaneshige.kenji@jp.fujitsu.com, warthog19@eaglescrag.net, Matthew Wilcox , kristen.c.accardi@intel.com On Thu, Feb 28, 2008 at 05:29:38PM -0700, Alex Chiang wrote: > Detect all physical PCI slots as described by ACPI, and create > entries in /sys/bus/pci/slots/. > > Not all physical slots are hotpluggable, and the acpiphp module > does not detect them. Now we know the physical PCI geography of > our system, without caring about hotplug. What is the guarantee that the names of these slots are correct and do not happen to be the same as the hotpluggable ones? Why show this information on machines that can not do anything with these slots at all? Will that not just confuse people? thanks, greg k-h