From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [patch] handle only block and class devices
Date: Tue, 14 Sep 2004 00:31:10 +0000 [thread overview]
Message-ID: <20040914003110.GA14829@vrfy.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 130 bytes --]
Fix a stupid logic bug, I introduced with the udev.c simplification. We
want to look at class and block devices only.
Sorry,
Kay
[-- Attachment #2: udev-bug-01.patch --]
[-- Type: text/plain, Size: 467 bytes --]
===== udev.c 1.61 vs edited =====
--- 1.61/udev.c 2004-09-07 17:48:42 +02:00
+++ edited/udev.c 2004-09-14 02:25:32 +02:00
@@ -122,7 +122,7 @@ int main(int argc, char *argv[], char *e
dbg("looking at '%s'", devpath);
/* we only care about class devices and block stuff */
- if (strstr(devpath, "class") && strstr(devpath, "block")) {
+ if (!strstr(devpath, "class") && !strstr(devpath, "block")) {
dbg("not a block or class device");
goto exit;
}
next reply other threads:[~2004-09-14 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 0:31 Kay Sievers [this message]
2004-09-14 5:58 ` [patch] handle only block and class 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=20040914003110.GA14829@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).