From: Ming Lei <tom.leiming@gmail.com>
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 5/5] initdev:kernel: USB and SCSI block init device notification, v3
Date: Tue, 5 May 2009 12:05:19 +0800 [thread overview]
Message-ID: <d82e647a0905042105g7639fc84g736668c371c40053@mail.gmail.com> (raw)
In-Reply-To: <20090505001950.GC29124@cuplxvomd02.corp.sa.net>
2009/5/5 David VomLehn <dvomlehn@cisco.com>:
> On Fri, May 01, 2009 at 11:55:39PM -0400, Ming Lei wrote:
>> On Fri, 1 May 2009 19:30:00 -0700
>> David VomLehn <dvomlehn@cisco.com> wrote:
>>
>> > From: Alan Stern <stern@rowland.harvard.edu
>> > diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
>> > index 6f51ca4..735b061 100644
>> > --- a/drivers/scsi/scsi_scan.c
>> > +++ b/drivers/scsi/scsi_scan.c
> ...
>> > @@ -1834,6 +1834,7 @@ static int do_scan_async(void *_data)
>> > struct async_scan_data *data = _data;
>> > do_scsi_scan_host(data->shost);
>> > scsi_finish_async_scan(data);
>> > + initdev_probe_done(BOOTDEV_BLOCK_MASK);
>>
>> Which code are waiting for the block device's probe done?
>
> None yet. That remains to be done.
>
Would you mind submitting the code path of waitting for probe done to allow a
intact review? Without the waitting code, it is a a little difficult
to undersand or verify
your patch, IMHO.
Thanks
--
Lei Ming
next prev parent reply other threads:[~2009-05-05 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 2:30 David VomLehn
2009-05-02 3:55 ` Ming Lei
2009-05-05 0:19 ` David VomLehn
2009-05-05 4:05 ` Ming Lei [this message]
2009-06-05 17:55 ` 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=d82e647a0905042105g7639fc84g736668c371c40053@mail.gmail.com \
--to=tom.leiming@gmail.com \
--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®