lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 29 Feb 2008 21:25:42 -0800 From: Greg KH <gregkh@...e.de> To: Alex Chiang <achiang@...com>, Gary Hade <garyhade@...ibm.com>, kaneshige.kenji@...fujitsu.com, warthog19@...lescrag.net, Matthew Wilcox <matthew@....cx>, kristen.c.accardi@...el.com, rick.jones2@...com, linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz, linux-acpi@...r.kernel.org Subject: Re: [PATCH 4/4] ACPI PCI slot detection driver 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists