[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200804164246.GA502540@kroah.com>
Date: Tue, 4 Aug 2020 18:42:46 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Daniel Gutson <daniel@...ypsium.com>
Cc: Derek Kiernan <derek.kiernan@...inx.com>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Arnd Bergmann <arnd@...db.de>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Richard Hughes <hughsient@...il.com>,
Alex Bazhaniuk <alex@...ypsium.com>
Subject: Re: [PATCH] Platform lockdown information in SYSFS
On Tue, Aug 04, 2020 at 11:37:02AM -0300, Daniel Gutson wrote:
> static void mypci_remove(struct pci_dev *pdev)
> {
> /*
> I tried enabling and disabling this
> if (child_device != NULL) {
> put_device(child_device);
> device_unregister(child_device);
> }
> */
You can just call device_destroy() here, but this should be the same.
But, if you have it commented out, that's not good, you have to clean
this up.
> class_remove_file(&my_class, &class_attr_howareyou);
You don't always have to remove files you create, but it doesn't hurt.
> class_unregister(&my_class);
class_destroy()? But this is the same as well, so all is good.
Try running without the above code commented out.
greg k-h
Powered by blists - more mailing lists