public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC PATCH] Multi-threaded device probing
Date: Wed, 26 Jul 2006 00:22:48 -0700	[thread overview]
Message-ID: <20060726072248.GA6249@suse.de> (raw)
In-Reply-To: <20060725155742.A15626@unix-os.sc.intel.com>

On Tue, Jul 25, 2006 at 03:57:42PM -0700, Keshavamurthy Anil S wrote:
> >    +       data = kmalloc(sizeof(*data), GFP_KERNEL);
> >    +       data->drv = drv;
> >    +       data->dev = dev;
> >    +
> > +	if (drv->multithread_probe) {
>             ^^^^^^^^^^^^^^^^^^^^^^
> 	 if (drv->multithread_probe && !cmdline_mtprobe) {
> 
> Also I think providing cmdline option to override the default 
> multithread probe behaviour would be good. Something like above
> which is useful while debugging the boot issues.

As this is going to be a bus specific option, one would think that the
individual busses would provide such a switch, if they wanted to or not.

thanks,

greg k-h

  reply	other threads:[~2006-07-26  7:27 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
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 [this message]
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=20060726072248.GA6249@suse.de \
    --to=gregkh@suse.de \
    --cc=anil.s.keshavamurthy@intel.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