[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2zFtWcytaIRWNqu@kroah.com>
Date: Thu, 10 Nov 2022 10:34:45 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] driver core: remove devm_device_remove_groups()
On Wed, Nov 09, 2022 at 01:10:59PM -0800, Dmitry Torokhov wrote:
> On Wed, Nov 09, 2022 at 03:11:47PM +0100, Rafael J. Wysocki wrote:
> > On Wed, Nov 9, 2022 at 3:07 PM Greg Kroah-Hartman
> > <gregkh@...uxfoundation.org> wrote:
> > >
> > > There is no in-kernel user of this function, so it is not needed anymore
> > > and can be removed.
> > >
> > > Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>
> > > Cc: "Rafael J. Wysocki" <rafael@...nel.org>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> >
> > For both patches in the series:
> >
> > Reviewed-by: Rafael J. Wysocki <rafael@...nel.org>
>
> I find it really weird to have an asymmetric core API...
I'm working on fixing up that asymmetric-ness. We have only one user of
devm_device_add_groups() and only a handful of devm_device_add_group()
left in the tree.
But it turns out that no one ever called these functions anyway, so they
aren't needed even if we did keep the "add" functions. So they should
be dropped no matter what.
thanks,
greg k-h
Powered by blists - more mailing lists