[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160108203737.GJ5354@localhost>
Date: Fri, 8 Jan 2016 14:37:37 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: linux-kernel@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
Phil Edworthy <phil.edworthy@...esas.com>,
Simon Horman <horms@...ge.net.au>,
Valentine Barshak <valentine.barshak@...entembedded.com>,
linux-pci@...r.kernel.org, linux-sh@...r.kernel.org
Subject: Re: [PATCH 0/2] drivers/pci: use builtin_platform_driver in renesas
On Mon, Dec 21, 2015 at 07:59:07PM -0500, Paul Gortmaker wrote:
> These two commits are extracted from what was a larger series[1] of
> demodularization in PCI host code that was bool Kconfig.
>
> With the other commits, there was some mixed opinions whether we
> should make it explicitly non-modular or move towards making it
> functionally working as a tristate in order to reduce the size of
> built-in code for multi-platform kernels.
>
> However with the renesas changes, there was no ".remove" and no
> "module_exit" code stripped out ; it is just a straight 1:1 mapping
> of the modular macros onto what they become in the non-modular case
> anyway -- meaning the runtime remains unchanged.
Is there any reason these drivers can't be made modular? I'd rather
do that, if we can.
Bjorn
Powered by blists - more mailing lists