Re: [RESEND RFT PATCH 2/2] mfd: max14577: Allow driver to be built as a module

From	Javier Martinez Canillas <javier@osg.samsung.com>
Newsgroups	linux.kernel
Subject	Re: [RESEND RFT PATCH 2/2] mfd: max14577: Allow driver to be built as a module
Date	2016-06-16 15:50 +0200
Message-ID	<rKFQd-za-5@gated-at.bofh.it> (permalink)
References	<rD6ud-iv-11@gated-at.bofh.it> <rD6ue-iv-29@gated-at.bofh.it> <rKD21-7fn-17@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Hello Lee,

On 06/16/2016 06:40 AM, Lee Jones wrote:
> On Thu, 26 May 2016, Javier Martinez Canillas wrote:
> 
>> The driver's Kconfig symbol is a boolean but nothing prevents the driver
>> to be built as a module instead of built-in. It is true that most system
>> integrators will choose the latter but the config should not restrict it.
> 
> Does the driver have all of the module related code?
>

Yes, it always did (even has a MODULE_DEVICE_TABLE so autoload should work)
but is just that the Kconfig symbol was bool instead of tristate since most
system integrators will choose to have it built-in.

Best regards,
-- 
Javier Martinez Canillas
Open Source Group
Samsung Research America

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [RESEND RFT PATCH 2/2] mfd: max14577: Allow driver to be built  as a module Lee Jones <lee.jones@linaro.org> - 2016-06-16 12:50 +0200
  Re: [RESEND RFT PATCH 2/2] mfd: max14577: Allow driver to be built as  a module Javier Martinez Canillas <javier@osg.samsung.com> - 2016-06-16 15:50 +0200

csiph-web