[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 04 Apr 2019 22:40:41 +0200
From: Robert Jarzmik <robert.jarzmik@...e.fr>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: rui.zhang@...el.com, edubezval@...il.com, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, Guenter Roeck <groeck@...omium.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Russell King <linux@...linux.org.uk>,
Ralf Baechle <ralf@...ux-mips.org>,
Paul Burton <paul.burton@...s.com>,
James Hogan <jhogan@...nel.org>, Guan Xuetao <gxt@....edu.cn>,
Andrew Morton <akpm@...ux-foundation.org>,
Alexey Brodkin <alexey.brodkin@...opsys.com>,
Arnd Bergmann <arnd@...db.de>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Daniel Mack <daniel@...que.org>,
linux-arm-kernel@...ts.infradead.org (moderated list:ARM PORT),
linux-mips@...r.kernel.org (open list:MIPS)
Subject: Re: [PATCH 1/7] thermal/drivers/core: Remove the module Kconfig's option
Daniel Lezcano <daniel.lezcano@...aro.org> writes:
> The module support for the thermal subsystem makes 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 the thermal
> to 'y'. The drivers can stay in tristate.
> - platforms need the thermal to be ready as soon as possible at boot time
> in order to mitigate
>
> Usually the subsystems framework are compiled-in and the plugs are as module.
>
> Remove the module option. The removal of the module related dead code will
> come after this patch gets in or is acked.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
> Acked-by: Guenter Roeck <groeck@...omium.org>
> For mini2440:
> Acked-by: Krzysztof Kozlowski <krzk@...nel.org>
For pxa:
Acked-by: Robert Jarzmik <robert.jarzmik@...e.fr>
Cheers.
--
Robert
Powered by blists - more mailing lists