On Fri, Feb 12, 2021 at 9:11 AM Uwe Kleine-König
<u.kleine-koenig(a)pengutronix.de> wrote:
nvdimm_remove is only ever called after nvdimm_probe() returned
successfully. In this case driver data is always set to a non-NULL value
so the check for driver data being NULL can go away as it's always false.
Looks good, thanks.