public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC PATCH] Multi-threaded device probing
Date: Tue, 25 Jul 2006 14:27:37 -0700	[thread overview]
Message-ID: <20060725212737.GB9513@suse.de> (raw)
In-Reply-To: <20060725210953.GA11405@martell.zuzino.mipt.ru>

On Wed, Jul 26, 2006 at 01:09:53AM +0400, Alexey Dobriyan wrote:
> On Tue, Jul 25, 2006 at 01:30:28PM -0700, Greg KH wrote:
> > This adds the infrastructure for drivers to do a threaded probe.
> 
> > -			goto ProbeFailed;
> > +			goto probe_failed;
> >  		}
> >  	} else if (drv->probe) {
> >  		ret = drv->probe(dev);
> >  		if (ret) {
> >  			dev->driver = NULL;
> > -			goto ProbeFailed;
> > +			goto probe_failed;
> >  		}
> >  	}
> >  	device_bind_driver(dev);
> >  	ret = 1;
> >  	pr_debug("%s: Bound Device %s to Driver %s\n",
> >  		 drv->bus->name, dev->bus_id, drv->name);
> > -	goto Done;
> > +	goto done;
> >  
> > - ProbeFailed:
> > +probe_failed:
> >  	if (ret == -ENODEV || ret == -ENXIO) {
> >  		/* Driver matched, but didn't support device
> >  		 * or device not found.
> > @@ -110,7 +99,53 @@ int driver_probe_device(struct device_dr
> >  		       "%s: probe of %s failed with error %d\n",
> >  		       drv->name, dev->bus_id, ret);
> >  	}
> > - Done:
> > +done:
> 
> Removing these changes will make this patch smaller and do one thing. ;-)

Heh, yeah, it would, but cleaning up coding style violations at the same
time that I move code around is usually safe :)

thanks,

greg k-h

  reply	other threads:[~2006-07-25 21:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 20:30 [RFC PATCH] Multi-threaded device probing Greg KH
2006-07-25 21:09 ` Alexey Dobriyan
2006-07-25 21:27   ` Greg KH [this message]
2006-07-25 21:27 ` H. Peter Anvin
2006-07-25 22:00 ` Dmitry Torokhov
2006-07-26  7:28   ` Greg KH
2006-07-25 22:15 ` James Courtier-Dutton
2006-07-26  0:08   ` Stefan Richter
2006-07-26  7:27     ` Greg KH
2006-07-26  7:24   ` Greg KH
2006-07-25 22:57 ` Keshavamurthy Anil S
2006-07-26  7:22   ` Greg KH
2006-07-26  0:34 ` Stefan Richter
2006-07-26  7:31   ` Greg KH
2006-07-26 11:29     ` Matthew Wilcox
2006-07-26 16:16       ` Greg KH
2006-07-26 16:42         ` Matthew Wilcox
2006-07-26 16:46           ` Greg KH
2006-07-27  0:02 ` Arnd Bergmann
2006-07-27  0:20   ` 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=20060725212737.GB9513@suse.de \
    --to=gregkh@suse.de \
    --cc=adobriyan@gmail.com \
    --cc=greg@kroah.com \
    --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