From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: stuyoder@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Of fsl_mc_allocator_driver_exit
Date: Fri, 15 Nov 2024 14:26:19 +0000 [thread overview]
Message-ID: <ZzdaC0_V6P-HsUdo@gallifrey> (raw)
In-Reply-To: <xly4pttb77ivx24tjd2zhqnrrwvvcdqdgdirvvshb2lugcbdq7@njdg5ogzho7u>
* Ioana Ciornei (ioana.ciornei@nxp.com) wrote:
> > * Dr. David Alan Gilbert (linux@treblig.org) wrote:
> > > Hi,
> > > One of my scripts noticed that fsl_mc_allocator_driver_exit()
> > > was added explicitly in
> > > commit 1e8ac83b6caf ("bus: fsl-mc: add fsl_mc_allocator cleanup function")
> > >
> > > but appears to be unused; given it's a cleanup function it feels like
> > > it should be wired up _somewhere_.
> > >
>
> I don't think that fsl_mc_allocator_driver_exit() is of any use at this
> point. The entire FSL_MC_BUS can only be built-in which means that there
> is no module_exit() which references it.
OK, well I'm happy to send a patch to clean it out, I was also
going to clean out fsl_mc_portal_reset().
> The same thing is true about the dprc_driver_exit() function.
Hmm, that's explicitly called from the error path of fsl_mc_bus_driver_init
Dave
> Ioana
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2024-11-15 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 13:49 Of fsl_mc_allocator_driver_exit Dr. David Alan Gilbert
2024-11-15 14:00 ` Dr. David Alan Gilbert
2024-11-15 14:22 ` Ioana Ciornei
2024-11-15 14:26 ` Dr. David Alan Gilbert [this message]
2024-11-15 14:29 ` Ioana Ciornei
2024-11-15 14:35 ` Dr. David Alan Gilbert
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=ZzdaC0_V6P-HsUdo@gallifrey \
--to=linux@treblig.org \
--cc=ioana.ciornei@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stuyoder@gmail.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