From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Schmaus <flo@geekplace.eu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] driver-core: print bus registration error value
Date: Tue, 15 May 2018 17:12:40 +0200 [thread overview]
Message-ID: <20180515151240.GC23553@kroah.com> (raw)
In-Reply-To: <20180515135114.31939-4-flo@geekplace.eu>
On Tue, May 15, 2018 at 03:51:14PM +0200, Florian Schmaus wrote:
> Signed-off-by: Florian Schmaus <flo@geekplace.eu>
> ---
> drivers/base/driver.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/driver.c b/drivers/base/driver.c
> index afd5b08b7677..c68d35139c0f 100644
> --- a/drivers/base/driver.c
> +++ b/drivers/base/driver.c
> @@ -149,8 +149,9 @@ int driver_register(struct device_driver *drv)
> struct device_driver *other;
>
> if (!drv->bus->p) {
> - printk(KERN_ERR "Driver '%s' was unable to register bus_type\n",
> - drv->name);
> + printk(KERN_ERR "Driver '%s' was unable to register bus_type "
> + "(error: %d)\n",
> + drv->name, drv->bus->bus_register_retval);
I don't understand, if a bus was never registered, this is going to fail
in lots of odd ways, including the value being 0, so that would show "no
error"? Is this really needed?
A better message would be something like:
"Driver '%s" was unable to register with bus_type '%s' because it was not initialized."
right?
thanks,
greg k-h
next prev parent reply other threads:[~2018-05-15 15:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 9:49 [PATCH] driver-core: Log the BUG() causing driver Florian Schmaus
2018-03-07 15:13 ` Greg Kroah-Hartman
2018-03-07 15:36 ` Florian Schmaus
2018-05-04 13:23 ` [PATCH v2] driver-core: Return EBUSY error instead of BUG_ON() Florian Schmaus
2018-05-04 17:37 ` Greg Kroah-Hartman
2018-05-04 17:38 ` Greg Kroah-Hartman
2018-05-15 13:51 ` [PATCH v3 0/3] return EINVAL " Florian Schmaus
2018-05-16 12:05 ` [PATCH v4 " Florian Schmaus
2018-05-16 16:08 ` [PATCH v5 " Florian Schmaus
2018-05-23 15:59 ` [PATCH v6 0/3] driver-core: " Florian Schmaus
2018-05-25 16:21 ` Greg Kroah-Hartman
2018-05-23 15:59 ` [PATCH v6 1/3] " Florian Schmaus
2018-05-23 15:59 ` [PATCH v6 2/3] driver-core: record error on bus registration Florian Schmaus
2018-05-23 15:59 ` [PATCH v6 3/3] driver-core: print bus registration error value Florian Schmaus
2018-05-16 16:08 ` [PATCH v5 1/3] driver-core: return EINVAL error instead of BUG_ON() Florian Schmaus
2018-05-16 16:35 ` Greg Kroah-Hartman
2018-05-16 16:08 ` [PATCH v5 2/3] driver-core: record error on bus registration Florian Schmaus
2018-05-16 16:35 ` Greg Kroah-Hartman
2018-05-16 16:08 ` [PATCH v5 3/3] driver-core: print bus registration error value Florian Schmaus
2018-05-16 16:37 ` Greg Kroah-Hartman
2018-05-16 12:05 ` [PATCH v4 1/3] driver-core: return EINVAL error instead of BUG_ON() Florian Schmaus
2018-05-16 15:39 ` Greg Kroah-Hartman
2018-05-16 16:07 ` Florian Schmaus
2018-05-16 12:05 ` [PATCH v4 2/3] driver-core: record error on bus registration Florian Schmaus
2018-05-17 13:08 ` kbuild test robot
2018-05-16 12:05 ` [PATCH v4 3/3] driver-core: print bus registration error value Florian Schmaus
2018-05-16 12:09 ` Florian Schmaus
2018-05-16 15:38 ` Greg Kroah-Hartman
2018-05-16 15:37 ` Greg Kroah-Hartman
2018-05-17 8:10 ` kbuild test robot
2018-05-15 13:51 ` [PATCH v3 1/3] driver-core: return EINVAL error instead of BUG_ON() Florian Schmaus
2018-05-15 15:10 ` Greg Kroah-Hartman
2018-05-15 15:13 ` Greg Kroah-Hartman
2018-05-15 13:51 ` [PATCH v3 2/3] driver-core: record error on bus registration Florian Schmaus
2018-05-16 8:50 ` kbuild test robot
2018-05-15 13:51 ` [PATCH v3 3/3] driver-core: print bus registration error value Florian Schmaus
2018-05-15 15:12 ` Greg Kroah-Hartman [this message]
2018-05-16 8:24 ` kbuild test robot
2018-05-16 8:35 ` kbuild test robot
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=20180515151240.GC23553@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=flo@geekplace.eu \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox