[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y44WEkKh9tdNjMlW@kroah.com>
Date: Mon, 5 Dec 2022 17:02:26 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Dawei Li <set_pte_at@...look.com>
Cc: johannes@...solutions.net, robert.jarzmik@...e.fr, jgross@...e.com,
sstabellini@...nel.org, oleksandr_tyshchenko@...m.com,
roger.pau@...rix.com, srinivas.kandagatla@...aro.org,
bgoswami@...cinc.com, mpe@...erman.id.au, npiggin@...il.com,
christophe.leroy@...roup.eu, kys@...rosoft.com,
haiyangz@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com,
alsa-devel@...a-project.org, linuxppc-dev@...ts.ozlabs.org,
xen-devel@...ts.xenproject.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/6] xen: make remove callback of xen driver void returned
On Mon, Dec 05, 2022 at 11:36:42PM +0800, Dawei Li wrote:
> Since commit fc7a6209d571 ("bus: Make remove callback return
> void") forces bus_type::remove be void-returned, it doesn't
> make much sense for any bus based driver implementing remove
> callbalk to return non-void to its caller.
Please wrap changelogs at 72 columns.
And this should go through the maintainers of the Xen bus code, not me,
right?
And why wasn't this attached to the 0/6 email properly? Did you use
different tools? If so, our tools can't find the link to keep them in
sync either :(
thanks,
greg k-h
Powered by blists - more mailing lists