From: Greg KH <greg@kroah.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: tom.leiming@gmail.com, kay.sievers@vrfy.org,
cornelia.huck@de.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: remove polling for driver_probe_done(v3)
Date: Wed, 4 Feb 2009 15:08:51 -0800 [thread overview]
Message-ID: <20090204230851.GF18484@kroah.com> (raw)
In-Reply-To: <20090130065224.47729f41@infradead.org>
On Fri, Jan 30, 2009 at 06:52:24AM -0800, Arjan van de Ven wrote:
> On Fri, 30 Jan 2009 20:48:35 +0800
> tom.leiming@gmail.com wrote:
>
> > From: Ming Lei <tom.leiming@gmail.com>
> >
> > This patch adds a function : driver_wait_probe_done,
> > which waits on condition of probing done to replace
> > polling for driver_probe_done in fs initialization.
> >
> > There is no better way to avoid polling for
> > driver_probe_done _and_ existence of the root device,
> > so we does not replace the driver_probe_done with
> > driver_wait_probe_done in such special case.
> >
> > Removing polling in fs initialization may lead to
> > a faster boot.
> >
> > Signed-off-by: Ming Lei <tom.leiming@gmail.com>
>
> ok this one will work fine ;)
>
> Reviewed-by: Arjan van de Ven <arjan@linux.intel.com>
>
> thanks for fixing this up
> (it will clash with the patch that moves this to one place, but the
> same cleanup can be done there)
What patch is that? Should i be taking this? Or are they in some other
tree?
thanks,
greg k-h
next prev parent reply other threads:[~2009-02-04 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 12:48 [PATCH] driver core: remove polling for driver_probe_done(v3) tom.leiming
2009-01-30 13:31 ` Cornelia Huck
2009-01-30 14:52 ` Arjan van de Ven
2009-02-04 23:08 ` Greg KH [this message]
2009-02-05 1:08 ` Arjan van de Ven
2009-02-05 18:08 ` Greg KH
2009-02-17 1:14 ` Ming Lei
2009-02-17 3:19 ` Greg KH
2009-02-17 4:07 ` Ming Lei
2009-02-17 4:12 ` 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=20090204230851.GF18484@kroah.com \
--to=greg@kroah.com \
--cc=arjan@infradead.org \
--cc=cornelia.huck@de.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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