From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: ske@pengutronix.de
Subject: Re: [PATCH 1/3] driver: make CONFIG_DEBUG_PROBES more useful for removal
Date: Fri, 16 Feb 2024 12:59:50 +0100 [thread overview]
Message-ID: <170808479062.1408984.10210208315888412124.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240215103353.2799723-1-a.fatoum@pengutronix.de>
On Thu, 15 Feb 2024 11:33:51 +0100, Ahmad Fatoum wrote:
> When CONFIG_DEBUG_PROBES is enabled, barebox will print a message on
> every device probe and removal. Unfortunately, the removal prints are not
> very useful, because the removal happens in the bus remove function,
> which is often a no-op, but that's not known to driver core.
>
> To make this a bit more useful, let's allow skipping bus remove
> functions like Linux does and only print that a remove is happening if
> either a bus or driver remove function is available.
>
> [...]
Applied, thanks!
[1/3] driver: make CONFIG_DEBUG_PROBES more useful for removal
https://git.pengutronix.de/cgit/barebox/commit/?id=4d515afe56eb (link may not be stable)
[2/3] drivers: drop simple bus remove in favor of common implementation
https://git.pengutronix.de/cgit/barebox/commit/?id=e8ec515026fd (link may not be stable)
[3/3] firmware: arm_scmi: call device driver remove if defined
https://git.pengutronix.de/cgit/barebox/commit/?id=59aab0bebb1b (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-02-16 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 10:33 Ahmad Fatoum
2024-02-15 10:33 ` [PATCH 2/3] drivers: drop simple bus remove in favor of common implementation Ahmad Fatoum
2024-02-15 10:33 ` [PATCH 3/3] firmware: arm_scmi: call device driver remove if defined Ahmad Fatoum
2024-02-16 11:59 ` Sascha Hauer [this message]
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=170808479062.1408984.10210208315888412124.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ske@pengutronix.de \
/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