Re: [PATCH] thermal/drivers/core: Remove the module Kconfig's option

2019-04-02 Thread Amit Kucheria
On Mon, Apr 1, 2019 at 10:24 AM Daniel Lezcano wrote: > > The module support for the thermal subsystem does have a little sense: > - some subsystems relying on it are not modules, thus forcing the >framework to be compiled in > - it is compiled in for almost every configs, the remaining ones

Re: [PATCH] thermal/drivers/core: Remove the module Kconfig's option

2019-04-01 Thread Daniel Lezcano
Hi Guenter, thanks for the review. On 01/04/2019 06:10, Guenter Roeck wrote: > On Sun, Mar 31, 2019 at 8:24 PM Daniel Lezcano > wrote: >> >> The module support for the thermal subsystem does have a little sense: > > Do you mean "makes little sense" ? yep :) >> - some subsystems relying on it

Re: [PATCH] thermal/drivers/core: Remove the module Kconfig's option

2019-04-01 Thread Krzysztof Kozlowski
On Mon, 1 Apr 2019 at 05:24, Daniel Lezcano wrote: > > The module support for the thermal subsystem does have a little sense: > - some subsystems relying on it are not modules, thus forcing the >framework to be compiled in > - it is compiled in for almost every configs, the remaining ones >

Re: [PATCH] thermal/drivers/core: Remove the module Kconfig's option

2019-03-31 Thread Guenter Roeck
On Sun, Mar 31, 2019 at 8:24 PM Daniel Lezcano wrote: > > The module support for the thermal subsystem does have a little sense: Do you mean "makes little sense" ? > - some subsystems relying on it are not modules, thus forcing the >framework to be compiled in > - it is compiled in for alm

[PATCH] thermal/drivers/core: Remove the module Kconfig's option

2019-03-31 Thread Daniel Lezcano
The module support for the thermal subsystem does have a little sense: - some subsystems relying on it are not modules, thus forcing the framework to be compiled in - it is compiled in for almost every configs, the remaining ones are a few platforms where I don't see why we can not switch t