summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2023-03-07 19:46:18 +0300
committerMark Brown <broonie@kernel.org>2023-03-07 19:46:18 +0300
commit2289fa0704b8d074d256cfa43ceaa6ee620d5697 (patch)
treefc07a93b930f0b09cb265606358b4cd3cd960b9a /Documentation/admin-guide
parent20064c47f63e995216e0dfb0a6ea37b653ed534c (diff)
parent3ffefa1d9c9eba60c7f8b4a9ce2df3e4c7f4a88e (diff)
downloadlinux-2289fa0704b8d074d256cfa43ceaa6ee620d5697.tar.xz
spi: Convert to platform remove callback returning
Merge series from Uwe Kleine-König <u.kleine-koenig@pengutronix.de>: This patch series adapts the platform drivers below drivers/spi to use the .remove_new() callback. Compared to the traditional .remove() callback .remove_new() returns no value. This is a good thing because the driver core doesn't (and cannot) cope for errors during remove. The only effect of a non-zero return value in .remove() is that the driver core emits a warning. The device is removed anyhow and an early return from .remove() usually yields a resource leak. By changing the remove callback to return void driver authors cannot reasonably assume any more that there is some kind of cleanup later. All drivers touched here returned zero unconditionally in their remove callback, so they could all be converted trivially to .remove_new().
Diffstat (limited to 'Documentation/admin-guide')
0 files changed, 0 insertions, 0 deletions