From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: don't wait for dummy devices
Date: Mon, 18 Oct 2004 16:55:14 +0000 [thread overview]
Message-ID: <20041018165514.GE6821@vrfy.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 52 bytes --]
No need to wait for dummy net devices.
Thanks,
Kay
[-- Attachment #2: wait-dummy-01.patch --]
[-- Type: text/plain, Size: 494 bytes --]
===== wait_for_sysfs.c 1.20 vs edited =====
--- 1.20/wait_for_sysfs.c 2004-10-15 23:54:11 +02:00
+++ edited/wait_for_sysfs.c 2004-10-18 18:53:13 +02:00
@@ -162,6 +162,7 @@
{ .subsystem = "net", .device = "lo" },
{ .subsystem = "net", .device = "tap" },
{ .subsystem = "net", .device = "ipsec" },
+ { .subsystem = "net", .device = "dummy" },
{ .subsystem = "net", .device = "irda" },
{ .subsystem = "sound", .device = NULL },
{ .subsystem = "printer", .device = "lp" },
next reply other threads:[~2004-10-18 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 16:55 Kay Sievers [this message]
2004-10-18 17:19 ` don't wait for dummy devices 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=20041018165514.GE6821@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).