From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751091AbaLPJys (ORCPT ); Tue, 16 Dec 2014 04:54:48 -0500 Received: from mout.kundenserver.de ([212.227.126.131]:63455 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750840AbaLPJyp (ORCPT ); Tue, 16 Dec 2014 04:54:45 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Stanimir Varbanov , Mark Rutland , devicetree@vger.kernel.org, Russell King , linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Kishon Vijay Abraham I , Bjorn Helgaas , Rob Herring , Kumar Gala , Grant Likely Subject: Re: [PATCH 4/5] PCI: qcom: Add Qualcomm PCIe controller driver Date: Tue, 16 Dec 2014 10:54:29 +0100 Message-ID: <4673431.OTm9MABNvH@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <548FFEB0.9080604@mm-sol.com> References: <1418404441-5518-1-git-send-email-svarbanov@mm-sol.com> <2577563.x0mEZJNVDQ@wuerfel> <548FFEB0.9080604@mm-sol.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:h6q574jxl7LX6UFBjL6KDoBM7j++2kr0elhy9CaoB9QsCE7/3Rv kFPJPROQ9fX2F+3jXs8wT08ihk63J1KDG6bpIq/AsguO0pgoeTTLEDXZHjOwEn0McMYwXPK PxeJCjyuwXmgESOFMGtHfC1tHgOzEFfyIDqNQid0tN0K/ha4APbZQl9vCuUhAFeio1g2prs Z4vM4bmlPePxjG/umAJbg== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 16 December 2014 11:43:12 Stanimir Varbanov wrote: > >> +static int __init qcom_pcie_probe(struct platform_device *pdev) > >> +{ > > > > I think it's a bug to mark this function as __init. It breaks > > deferred probing and detaching/reattaching the device trough sysfs. > > > > My bad, I have tried to avoid mismatch section warnings came up from > dw_pcie_host_init() which is annotated as __init. Do you think we need > to remove __init from dw_pcie_host_init() declaration and fix the > drivers accordingly? Yes, that's probably best. Initially, it was ok because all front-ends of the dw-pcie driver were using module_platform_probe(), but that is not the case any more, so now at least keystone, layerscape and spear13xx are broken, and I think it's safer to change dw_pcie_host_init than to rely on everyone using module_platform_probe() correctly. Arnd