device-dax: Drop an empty .remove callback
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>
This commit is contained in:
parent
e307bf11c5
commit
c80b53204d
@ -452,15 +452,9 @@ int dev_dax_probe(struct dev_dax *dev_dax)
|
|||||||
}
|
}
|
||||||
EXPORT_SYMBOL_GPL(dev_dax_probe);
|
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 = {
|
static struct dax_device_driver device_dax_driver = {
|
||||||
.probe = dev_dax_probe,
|
.probe = dev_dax_probe,
|
||||||
.remove = dev_dax_remove,
|
/* all probe actions are unwound by devm, so .remove isn't necessary */
|
||||||
.match_always = 1,
|
.match_always = 1,
|
||||||
};
|
};
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user