Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755369Ab2JDUO6 (ORCPT ); Thu, 4 Oct 2012 16:14:58 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:35993 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751535Ab2JDUOy (ORCPT ); Thu, 4 Oct 2012 16:14:54 -0400 MIME-Version: 1.0 In-Reply-To: References: <1349305214-3241-1-git-send-email-yinghai@kernel.org> <20121004174746.GA24119@google.com> Date: Thu, 4 Oct 2012 13:14:52 -0700 X-Google-Sender-Auth: v75NB6GqSTJKxp2sloMYM3Py5_k Message-ID: Subject: Re: [PATCH 0/4] ACPI: kill acpi_pci_root_start From: Yinghai Lu To: Bjorn Helgaas Cc: Len Brown , Greg Kroah-Hartman , Andrew Morton , Linus Torvalds , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 934 Lines: 20 On Thu, Oct 4, 2012 at 12:44 PM, Bjorn Helgaas wrote: > > To answer your specific question, yes, I do think drivers that are > statically built in probably should be registered before devices are > enumerated. That way, the boot-time case is more similar to the > hot-add case. > > Obviously, for drivers that can be modules, the reverse must work as > well (enumerate devices, then load and register the driver). And then > the other order (register driver, then enumerate device) must also > work so future hot-adds of the same device type work. so you will have to handle two paths instead one. current booting path sequence are tested more than hot add path. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/