[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2uu5Q7mLzS0w9VR@kroah.com>
Date: Wed, 9 Nov 2022 14:45:09 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Dawei Li <set_pte_at@...look.com>
Cc: rafael@...nel.org, u.kleine-koenig@...gutronix.de,
dvhart@...radead.org, andy@...radead.org, lenb@...nel.org,
arnd@...db.de, peterhuewe@....de, kys@...rosoft.com,
kronos.it@...il.com, dmitry.torokhov@...il.com,
bleung@...omium.org, sujith.thomas@...el.com, vithampi@...are.com,
lee@...nel.org, wim@...ux-watchdog.org, jgross@...e.com,
davem@...emloft.net, linux-acpi@...r.kernel.org,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] acpi: make remove callback of acpi driver void
On Sun, Nov 06, 2022 at 10:57:53PM +0800, Dawei Li wrote:
> For bus-based driver, device removal is implemented as:
> 1 device_remove()->
> 2 bus->remove()->
> 3 driver->remove()
>
> Driver core needs _no_ inform from callee(bus driver) about the
> result of remove callback. In that case,
> commit <fc7a6209d571> ("bus: Make remove callback return void")
> forces struct bus_type::remove() be void-returned.
>
> Now we have the situation that both 1 & 2 of calling chain are
> void-returned, so it does _not_ make much sense for 3(driver->remove)
> to return non-void to its caller.
>
> So the basic idea behind this change is making remove() callback of
> any bus-based driver to be void-returned.
>
> This change itself, is for device drivers based on acpi-bus.
>
> Signed-off-by: Dawei Li <set_pte_at@...look.com>
As RFC patches don't mean to be applied, I'll wait for a real version to
be submitted before reviewing this.
thanks,
greg k-h
Powered by blists - more mailing lists