From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: RE: wait_for_sysfs() "class specific file unavailable" messagesfor
Date: Fri, 10 Dec 2004 21:05:37 +0000 [thread overview]
Message-ID: <1102712738.6011.0.camel@localhost.localdomain> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12E808@xbl3.ma.emulex.com>
On Fri, 2004-12-10 at 10:05 -0500, James.Smart@Emulex.Com wrote:
> Kay,
>
> > What does "ls -l /class/fc_host/host35" print? We may wait for a
> > specific file, if there is one.
>
> The results are below....
>
> I do need to caveat this that this is for a pending patch, which although
> it has general consensus, has not made it into the upstream as yet.
I've added it to the list.
Thanks,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-12-10 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 16:04 wait_for_sysfs() "class specific file unavailable" messages for /class/fc_host and /class/fc_transpo James.Smart
2004-12-02 18:47 ` wait_for_sysfs() "class specific file unavailable" messages Kay Sievers
2004-12-02 22:20 ` wait_for_sysfs() "class specific file unavailable" messages for /class/fc_host and /class/fc_tra Greg KH
2004-12-10 15:05 ` wait_for_sysfs() "class specific file unavailable" messagesfor /class/fc_host and /class/fc_tran James.Smart
2004-12-10 21:05 ` Kay Sievers [this message]
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=1102712738.6011.0.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.