From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: linux-kernel@vger.kernel.org, Karsten Keil <isdn@linux-pingi.de>,
netdev@vger.kernel.org
Subject: Re: [PATCH] mISDN: remove unneeded mISDN_class_release()
Date: Thu, 30 Mar 2023 08:01:07 +0200 [thread overview]
Message-ID: <ZCUlo1jcPeU4K_AI@kroah.com> (raw)
In-Reply-To: <ZCST8vuQDEo9GhsS@corigine.com>
On Wed, Mar 29, 2023 at 09:39:30PM +0200, Simon Horman wrote:
> On Wed, Mar 29, 2023 at 08:01:27AM +0200, Greg Kroah-Hartman wrote:
> > The mISDN_class_release() is not needed at all, as the class structure
> > is static, and it does not actually do anything either, so it is safe to
> > remove as struct class does not require a release callback.
> >
> > Cc: Karsten Keil <isdn@linux-pingi.de>
> > Cc: netdev@vger.kernel.org
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> > Note: I would like to take this through the driver-core tree as I have
> > later struct class cleanups that depend on this change being made to the
> > tree if that's ok with the maintainer of this file.
> >
> > drivers/isdn/mISDN/core.c | 6 ------
> > 1 file changed, 6 deletions(-)
>
> I assume this will hit the following in drivers/base/class.c:class_release():
>
> if (class->class_release)
> class->class_release(class);
> else
> pr_debug("class '%s' does not have a release() function, "
> "be careful\n", class->name);
>
> So I also assume that you are being careful :)
Yes, I am :)
I need to remove that debug line soon as I'm moving all struct class
instances to be static and in read-only memory, which would mean that no
release function is needed at all for them. Give me a few hundred more
commits to get there...
thanks for the review!
greg k-h
next prev parent reply other threads:[~2023-03-30 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 6:01 [PATCH] mISDN: remove unneeded mISDN_class_release() Greg Kroah-Hartman
2023-03-29 19:39 ` Simon Horman
2023-03-30 6:01 ` Greg Kroah-Hartman [this message]
2023-03-30 7:19 ` Simon Horman
2023-03-31 6:17 ` Jakub Kicinski
2023-03-31 7:04 ` Greg Kroah-Hartman
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=ZCUlo1jcPeU4K_AI@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.com \
/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;
as well as URLs for NNTP newsgroup(s).