device-dax: Drop an empty .remove callback
authorUwe Kleine-König <uwe@kleine-koenig.org>
Fri, 5 Feb 2021 22:28:41 +0000 (23:28 +0100)
committerDan Williams <dan.j.williams@intel.com>
Wed, 17 Feb 2021 03:44:40 +0000 (19:44 -0800)
The dax core properly handles a dax driver not having a remove callback.
So drop it without changing the effective behaviour.

Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
Link: https://lore.kernel.org/r/20210205222842.34896-5-uwe@kleine-koenig.org
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
drivers/dax/device.c

index 5da2980bb16b99cb699de486bf72a1a522081022..db92573c94e864109680d613e52b194f7774a874 100644 (file)
@@ -452,15 +452,9 @@ int dev_dax_probe(struct dev_dax *dev_dax)
 }
 EXPORT_SYMBOL_GPL(dev_dax_probe);
 
-static int dev_dax_remove(struct dev_dax *dev_dax)
-{
-       /* all probe actions are unwound by devm */
-       return 0;
-}
-
 static struct dax_device_driver device_dax_driver = {
        .probe = dev_dax_probe,
-       .remove = dev_dax_remove,
+       /* all probe actions are unwound by devm, so .remove isn't necessary */
        .match_always = 1,
 };