lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAPcyv4jVw6o7Yznxs7UDMnSoJLozx86v5YCg6YZGeGm6emyooQ@mail.gmail.com> Date: Tue, 16 Feb 2021 19:37:58 -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 2/2] libnvdimm: Make remove callback return void On Fri, Feb 12, 2021 at 9:21 AM Uwe Kleine-König <u.kleine-koenig@...gutronix.de> wrote: > > All drivers return 0 in their remove callback and the driver core ignores > the return value of nvdimm_bus_remove() anyhow. So simplify by changing > the driver remove callback to return void and return 0 unconditionally > to the upper layer. Looks good, thanks.
Powered by blists - more mailing lists