From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: David VomLehn <dvomlehn@cisco.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-usb@vger.kernel.org, greg@kroah.com,
linux-scsi@vger.kernel.org, netdev@vger.kernel.org,
arjan@infradead.org
Subject: Re: [PATCH 7/7] initdev:kernel:Await block device discovery
Date: Tue, 09 Jun 2009 00:55:01 +0200 [thread overview]
Message-ID: <4A2D96C5.2080604@s5r6.in-berlin.de> (raw)
In-Reply-To: <20090608223019.GC22222@cuplxvomd02.corp.sa.net>
David VomLehn wrote:
> On Sat, Jun 06, 2009 at 06:04:38AM -0400, Stefan Richter wrote:
>> 1.) It depends on the rootdelay so big that it is guaranteed that one
>> or more initdev_found() have been called before prepare_namespace()'s
>> ssleep(root_delay) is over.
...
> I think you misunderstood. Buses are enumerated before this code is
> reached and thus initdev_found() has already been called for all attached
> block devices.
...
> I would appreciate it if you could take a closer look at the locations where
> initdev_found() and initdev_probe_done() are called and see if you still
> think there is a problem.
I obviously need to do that.
However, one issue remains: If somebody wants to use your API for
another bus, he needs to know at which point he can successfully use it,
and after what point (or context) it cannot, even must not, be used
anymore. This isn't documented --- or is it?
(By 'buses are enumerated before...' you surely mean only the buses for
which you implemented this API usage already.)
--
Stefan Richter
-=====-==--= -==- -=--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-06-08 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 2:34 David VomLehn
2009-06-06 10:04 ` Stefan Richter
2009-06-08 22:30 ` David VomLehn
2009-06-08 22:55 ` Stefan Richter [this message]
2009-06-08 23:13 ` David VomLehn
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=4A2D96C5.2080604@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=dvomlehn@cisco.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®