Message ID | 20230303185445.2112695-1-u.kleine-koenig@pengutronix.de |
---|---|
Headers | show |
Series | pwm: Convert to platform remove callback returning void | expand |
Hello: This patch was applied to chrome-platform/linux.git (for-kernelci) by Thierry Reding <thierry.reding@gmail.com>: On Fri, 3 Mar 2023 19:54:15 +0100 you wrote: > Hello, > > this patch series adapts the platform drivers below drivers/pwm 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. > > [...] Here is the summary with links: - [09/30] pwm: cros-ec: Convert to platform remove callback returning void https://git.kernel.org/chrome-platform/c/159a61a7b5b0 You are awesome, thank you!
Hello: This patch was applied to chrome-platform/linux.git (for-next) by Thierry Reding <thierry.reding@gmail.com>: On Fri, 3 Mar 2023 19:54:15 +0100 you wrote: > Hello, > > this patch series adapts the platform drivers below drivers/pwm 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. > > [...] Here is the summary with links: - [09/30] pwm: cros-ec: Convert to platform remove callback returning void https://git.kernel.org/chrome-platform/c/159a61a7b5b0 You are awesome, thank you!