From: Greg KH <gregkh@linuxfoundation.org>
To: Angus Chen <angus.chen@jaguarmicro.com>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: core: Add more print info for bus remove and driver remove
Date: Tue, 27 Aug 2024 15:18:49 +0200 [thread overview]
Message-ID: <2024082705-decoy-disk-6461@gregkh> (raw)
In-Reply-To: <20240827125244.1747-1-angus.chen@jaguarmicro.com>
On Tue, Aug 27, 2024 at 08:52:44PM +0800, Angus Chen wrote:
> When enable initcall_debug,some devices call bus remove,
> Some devices call driver remove.
>
> Signed-off-by: Angus Chen <angus.chen@jaguarmicro.com>
> ---
> drivers/base/core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index 8c0733d3aad8..ff965cd51bcf 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -4833,11 +4833,11 @@ void device_shutdown(void)
> }
> if (dev->bus && dev->bus->shutdown) {
> if (initcall_debug)
> - dev_info(dev, "shutdown\n");
> + dev_info(dev, "call bus shutdown\n");
> dev->bus->shutdown(dev);
> } else if (dev->driver && dev->driver->shutdown) {
> if (initcall_debug)
> - dev_info(dev, "shutdown\n");
> + dev_info(dev, "call driver shutdown\n");
I do not understand, why is this needed? Who needs it and what is going
to rely on it?
Really, this should be moved to dev_dbg() instead, right?
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-27 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 12:52 [PATCH] drivers: core: Add more print info for bus remove and driver remove Angus Chen
2024-08-27 13:18 ` Greg KH [this message]
2024-08-28 2:11 ` Angus Chen
2024-09-03 11:04 ` Greg KH
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=2024082705-decoy-disk-6461@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=angus.chen@jaguarmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.