diff options
| author | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2023-11-05 18:00:36 +0300 |
|---|---|---|
| committer | Damien Le Moal <dlemoal@kernel.org> | 2023-11-08 03:00:03 +0300 |
| commit | 36f10a914a7b7169b5e399d1671ba2169c0801f3 (patch) | |
| tree | 9e530d932dadc289d8d378fe76fd07313031614f /net/unix/unix_bpf.c | |
| parent | fd3a6837d8e18cb7be80dcca1283276290336a7a (diff) | |
| download | linux-36f10a914a7b7169b5e399d1671ba2169c0801f3.tar.xz | |
ata: pata_falcon: 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: Sergey Shtylyov <s.shtylyov@omp.ru>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Diffstat (limited to 'net/unix/unix_bpf.c')
0 files changed, 0 insertions, 0 deletions