diff options
| author | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2023-11-05 00:15:03 +0300 |
|---|---|---|
| committer | Sebastian Reichel <sebastian.reichel@collabora.com> | 2023-11-16 01:15:37 +0300 |
| commit | 099806de68b75a0fe114376b1ee162fdff572ecc (patch) | |
| tree | da9aa7d2788b267c80e07ae6388d321fe1d8f9de /net/smc/smc_netlink.c | |
| parent | dfcb264a01a9199e8338a548731baf5bbe77ef19 (diff) | |
| download | linux-099806de68b75a0fe114376b1ee162fdff572ecc.tar.xz | |
power: reset: at91-poweroff: Stop using module_platform_driver_probe()
On today's platforms the benefit of platform_driver_probe() isn't that
relevant any more. It allows to drop some code after booting (or module
loading) for .probe() and discard the .remove() function completely if
the driver is built-in. This typically saves a few 100k.
The downside of platform_driver_probe() is that the driver cannot be
bound and unbound at runtime which is ancient and so slightly
complicates testing. There are also thoughts to deprecate
platform_driver_probe() because it adds some complexity in the driver
core for little gain. Also many drivers don't use it correctly. This
driver for example misses to mark the driver struct with __ref which is
needed to suppress a (W=1) modpost warning.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
Link: https://lore.kernel.org/r/20231104211501.3676352-17-u.kleine-koenig@pengutronix.de
Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Diffstat (limited to 'net/smc/smc_netlink.c')
0 files changed, 0 insertions, 0 deletions