On Fri, Nov 15, 2019 at 02:48:37PM +0100, [email protected] wrote: > From: Patrick Rudolph <[email protected]> > > Fix a bug where the kernel module can't be loaded after it has been > unloaded as the devices are still present and conflicting with the > to be created coreboot devices. > > Signed-off-by: Patrick Rudolph <[email protected]> > --- > drivers/firmware/google/coreboot_table.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/drivers/firmware/google/coreboot_table.c > b/drivers/firmware/google/coreboot_table.c > index 8d132e4f008a..88c6545bebf4 100644 > --- a/drivers/firmware/google/coreboot_table.c > +++ b/drivers/firmware/google/coreboot_table.c > @@ -163,8 +163,14 @@ static int coreboot_table_probe(struct platform_device > *pdev) > return ret; > } > > +static int __cb_dev_unregister(struct device *dev, void *dummy) > +{ > + device_unregister(dev);
Did you build this patch??? Did it work when you tested it? How? Please fix up, greg k-h _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
