From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] driver core: remove devm_device_remove_groups()
Date: Thu, 10 Nov 2022 10:34:45 +0100 [thread overview]
Message-ID: <Y2zFtWcytaIRWNqu@kroah.com> (raw)
In-Reply-To: <Y2wXYxrr/qed/j//@google.com>
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@linuxfoundation.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@gmail.com>
> > > Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >
> > For both patches in the series:
> >
> > Reviewed-by: Rafael J. Wysocki <rafael@kernel.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
next prev parent reply other threads:[~2022-11-10 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 14:07 [PATCH 1/2] driver core: remove devm_device_remove_groups() Greg Kroah-Hartman
2022-11-09 14:07 ` [PATCH 2/2] driver core: remove devm_device_remove_group() Greg Kroah-Hartman
2022-11-09 14:11 ` [PATCH 1/2] driver core: remove devm_device_remove_groups() Rafael J. Wysocki
2022-11-09 21:10 ` Dmitry Torokhov
2022-11-10 9:34 ` Greg Kroah-Hartman [this message]
2022-11-10 13:07 ` Rafael J. Wysocki
2022-11-10 17:14 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2zFtWcytaIRWNqu@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox