From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <20121207062530.11051.47869.stgit@amt.stowe> References: <20121207062454.11051.12739.stgit@amt.stowe> <20121207062530.11051.47869.stgit@amt.stowe> Date: Thu, 6 Dec 2012 22:48:42 -0800 Message-ID: Subject: Re: [PATCH 06/15] PCI/acpiphp: Convert "acpiphp" sub-driver's functionality to built-in only From: Yinghai Lu To: Myron Stowe Cc: bhelgaas@google.com, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-acpi-owner@vger.kernel.org List-ID: On Thu, Dec 6, 2012 at 10:25 PM, Myron Stowe wrote: > The "ACPI Hot Plug PCI Controller ("acpiphp")" sub-driver may be compiled > as a module. Kernel modules are instantiated somewhat randomly - the > order in which they are linked as the kernel as built - thus if there are > any dependencies on the ordering of attaching sub-drivers, they can not be > effectively dealt with. > > This patch series resolves any potential sequencing inter-dependencies by > converting "acpiphp" sub-driver's functionality to being only supported as > statically built-in to the kernel. Inter-dependencies can then be > effectively handled by explicitly sequencing the addition of such > functionality. some slots may support both acpiphp and pciehp. if make acpiphp to be built-in, user do not have choice anymore. Thanks Yinghai