Hello Daniel, On Thu, Apr 06, 2023 at 03:54:11PM +0200, Daniel Lezcano wrote: > On 13/03/2023 08:54, Uwe Kleine-König wrote: > > this patch series adapts the platform drivers below drivers/clk > > 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. > > > > Most clocksource drivers are not supposed to be removed. Two drivers are > > adapted here to actually prevent removal. One driver is fixed not to > > return an error code in .remove() and then the two remaining drivers > > with a remove callback are trivially converted to .remove_new(). > > > > Applied and fixed up patch #2 Great. Thank you. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | https://www.pengutronix.de/ |
Attachment:
signature.asc
Description: PGP signature
