From: Greg KH <gregkh@suse.de>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: drivers/base: device_bind_driver() fix
Date: Wed, 24 Jan 2007 15:42:59 -0800 [thread overview]
Message-ID: <20070124234259.GB2160@suse.de> (raw)
In-Reply-To: <20070124171441.6a07d06b@localhost.localdomain>
On Wed, Jan 24, 2007 at 05:14:41PM +0300, Vitaly Bordug wrote:
>
> Keeps sysfs from creating link if device is already bound to driver.
> Similar behavior was before the rework;
Which "rework" caused this?
> now without this patch fixed PHY will complain about not been able to
> create file in sysfs.
Which device is being bound to a driver before it is registered? I know
the i2c layer does it, but I haven't had any people reporting issues
there.
> Signed-off-by: Vitaly Bordug <vbordug@ru.mvista.com>
> ---
>
> drivers/base/dd.c | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/dd.c b/drivers/base/dd.c
> index 510e788..6da3d01 100644
> --- a/drivers/base/dd.c
> +++ b/drivers/base/dd.c
> @@ -26,12 +26,12 @@
> #define to_drv(node) container_of(node, struct device_driver, kobj.entry)
>
>
> -static void driver_bound(struct device *dev)
> +static int driver_bound(struct device *dev)
> {
> if (klist_node_attached(&dev->knode_driver)) {
> printk(KERN_WARNING "%s: device %s already bound\n",
> __FUNCTION__, kobject_name(&dev->kobj));
> - return;
> + return 0;
> }
>
> pr_debug("bound device '%s' to driver '%s'\n",
> @@ -42,6 +42,7 @@ static void driver_bound(struct device *dev)
> BUS_NOTIFY_BOUND_DRIVER, dev);
>
> klist_add_tail(&dev->knode_driver, &dev->driver->klist_devices);
> + return 1;
Please return 0 for "good" and -ERRORSOMETHING for a when a problem
happens, like the rest of the kernel.
thanks,
greg k-h
prev parent reply other threads:[~2007-01-24 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 14:14 drivers/base: device_bind_driver() fix Vitaly Bordug
2007-01-24 23:42 ` Greg KH [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=20070124234259.GB2160@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vbordug@ru.mvista.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