From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752240AbcHHVMg (ORCPT ); Mon, 8 Aug 2016 17:12:36 -0400 Received: from mail-ua0-f179.google.com ([209.85.217.179]:36183 "EHLO mail-ua0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750929AbcHHVMf (ORCPT ); Mon, 8 Aug 2016 17:12:35 -0400 MIME-Version: 1.0 In-Reply-To: References: <20160712193645.9098-1-atull@opensource.altera.com> <20160712193645.9098-7-atull@opensource.altera.com> From: Moritz Fischer Date: Mon, 8 Aug 2016 13:44:59 -0700 Message-ID: Subject: Re: [PATCH v18 6/6] ARM: socfpga: fpga bridge driver support To: atull Cc: Paul Gortmaker , Rob Herring , Mark Rutland , Greg Kroah-Hartman , Ian Campbell , Dinh Nguyen , Devicetree List , "linux-arm-kernel@lists.infradead.org" , LKML , Alan Tull , Matthew Gerlach Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@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