[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4gqXpQK5ta9enky1MrGVYAGa09DaJHod5CK9Ybe59772w@mail.gmail.com>
Date: Tue, 16 Feb 2021 17:40:53 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Ira Weiny <ira.weiny@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
kernel@...gutronix.de, linux-nvdimm <linux-nvdimm@...ts.01.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] libnvdimm: simplify nvdimm_remove()
On Fri, Feb 12, 2021 at 9:11 AM Uwe Kleine-König
<u.kleine-koenig@...gutronix.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.
Powered by blists - more mailing lists