On Thu, Aug 25, 2022 at 10:01:58PM +0200, Andy Shevchenko wrote: > On Wed, Aug 24, 2022 at 1:46 PM Vincent Whitchurch > <vincent.whitchurch@xxxxxxxx> wrote: > > > > Use devm_* functions in probe to remove some code and to make it easier > > to add further calls to the probe function. > > ... > > > + mutex_init(&adc->lock); > > > + return devm_iio_device_register(&spi->dev, indio_dev); > > Do you still need to destroy the mutex? If so, you may not call devm_ > variant of iio_device_register() or you have to wrap mutex_destroy() > accordingly. mutex_destroy() is only used to ensure that mutex debugging catches further use of the mutex. Isn't it rather overkill to add specific cleanup to do only that, especially in this case when it's anyway going to get freed immediately afterwards? The vast majority of IIO drivers don't call mutex_destroy() (256 calls to mutex_init() in HEAD vs 12 to mutex_destroy()).
