From: Stelian Pop <stelian@popies.net>
To: Greg KH <greg@kroah.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: usb sysfs intf files no longer created when probe fails
Date: Wed, 22 Jun 2005 20:27:36 +0200 [thread overview]
Message-ID: <1119464856.5080.4.camel@deep-space-9.dsnet> (raw)
In-Reply-To: <20050622162221.GB2274@kroah.com>
Le mercredi 22 juin 2005 à 09:22 -0700, Greg KH a écrit :
> On Wed, Jun 22, 2005 at 05:53:28PM +0200, Stelian Pop wrote:
> > Le mercredi 22 juin 2005 ?? 11:41 -0400, Alan Stern a ??crit :
> >
> > > This is a curious aspect of the driver model core. Should failure of a
> > > driver to bind be considered serious enough to cause device_add to fail?
> > > The current answer is Yes unless the driver's probe routine returns
> > > -ENODEV or -ENXIO, in which case the failure is not considered serious.
> >
> > Indeed. I've also tracked my problem down to the hid core which returns
> > -EIO when it fails to drive an unknown HID device, instead of a more
> > logical -ENODEV (this is not a failure to init a known device, but
> > rather the impossibility to init an unknown device).
> >
> > The patch below solves the problem for me:
>
> Damm, beat me by a few minutes :)
:)
> Yes, this is the proper fix for this.
>
> But to answer Alan's main question, I think you are correct, we should
> not fail device_add if binding a device fails. I can see this causing a
> lot of very difficult problems in the future (including the fact that
> I've been hitting this bug with a new driver I'm writing and didn't even
> realize it...)
>
> So, I'll apply this one, and revert the main part of Hannes's patch too.
Thanks.
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2005-06-22 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 13:50 usb sysfs intf files no longer created when probe fails Stelian Pop
2005-06-22 14:07 ` [linux-usb-devel] " Stelian Pop
2005-06-22 14:56 ` Stelian Pop
2005-06-22 16:03 ` Alan Stern
2005-06-22 18:33 ` Stelian Pop
2005-06-22 16:17 ` Greg KH
2005-06-22 14:59 ` Greg KH
2005-06-22 15:09 ` [linux-usb-devel] " Stelian Pop
2005-06-22 15:41 ` Alan Stern
2005-06-22 15:53 ` Stelian Pop
2005-06-22 16:22 ` Greg KH
2005-06-22 18:27 ` Stelian Pop [this message]
2005-06-22 16:26 ` Greg KH
2005-06-22 18:25 ` Stelian Pop
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=1119464856.5080.4.camel@deep-space-9.dsnet \
--to=stelian@popies.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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