From mboxrd@z Thu Jan 1 00:00:00 1970 From: Moritz Fischer Subject: Re: [PATCH v18 6/6] ARM: socfpga: fpga bridge driver support Date: Mon, 8 Aug 2016 13:44:59 -0700 Message-ID: References: <20160712193645.9098-1-atull@opensource.altera.com> <20160712193645.9098-7-atull@opensource.altera.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: atull Cc: Mark Rutland , Devicetree List , Ian Campbell , Matthew Gerlach , Greg Kroah-Hartman , LKML , Paul Gortmaker , Rob Herring , Dinh Nguyen , Alan Tull , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org Hi Alan, On Mon, Aug 8, 2016 at 12:18 PM, atull wrote: >> Please don't use module.h in drivers controlled by a bool >> Kconfig setting. >> >> THanks, >> Paul. >> > > Thanks for the feedback. Can you provide an example of what you > would consider to be proper usage in the kernel? I think Paul is suggesting to use static int __init alt_fpga_bridge_init(void) { platform_driver_register(&alt_fpga_bridge_driver); } device_initcall(alt_fpga_bridge_init); or better: builtin_platform_driver(&alt_fpga_bridge_driver); Like for example in: drivers/cpuidle/cpuidle-mvebu-v7.c Cheers, Moritz