From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 1/3] driver: call devinfo_del() during free_device_res()
Date: Thu, 27 Nov 2025 12:34:14 +0100 [thread overview]
Message-ID: <20251127113416.2740774-1-s.hauer@pengutronix.de> (raw)
devinfo_del() can safely be called mutiple times. Call it from
free_device_res() so that remaining resources are freed before the
device goes out of scope.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
drivers/base/driver.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/base/driver.c b/drivers/base/driver.c
index eca23d7c30..eefed4b1a5 100644
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -348,6 +348,7 @@ EXPORT_SYMBOL(unregister_device);
*/
void free_device_res(struct device *dev)
{
+ devinfo_del(dev, NULL);
free(dev->unique_name);
dev->unique_name = NULL;
free(dev->deferred_probe_reason);
@@ -825,10 +826,11 @@ void devinfo_del(struct device *dev, void (*info)(struct device *))
devinfo_init(dev);
list_for_each_entry_safe(cb, tmp, &dev->info_list, list) {
- if (cb->info == info) {
- list_del(&cb->list);
- free(cb);
- }
+ if (info && cb->info != info)
+ continue;
+
+ list_del(&cb->list);
+ free(cb);
}
}
--
2.47.3
next reply other threads:[~2025-11-27 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 11:34 Sascha Hauer [this message]
2025-11-27 11:34 ` [PATCH 2/3] driver: call free_device_res() from unregister_device() Sascha Hauer
2025-11-27 11:34 ` [PATCH 3/3] dm: fix memory leak Sascha Hauer
2025-11-28 7:11 ` [PATCH 1/3] driver: call devinfo_del() during free_device_res() Sascha Hauer
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=20251127113416.2740774-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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