aboutsummaryrefslogtreecommitdiffstats
path: root/udev.c
diff options
context:
space:
mode:
authorkay.sievers@vrfy.org <kay.sievers@vrfy.org>2004-03-23 18:54:34 -0800
committerGreg KH <gregkh@suse.de>2005-04-26 21:35:10 -0700
commit2a94c8777eacff16821a06368092852f7b42882f (patch)
treef552dc005178063b6ef6fb6abf0310e28bbf83e9 /udev.c
parent4474484153f529c1a1c11392e8fc3fa8a588de54 (diff)
downloadudev-2a94c8777eacff16821a06368092852f7b42882f.tar.gz
[PATCH] don't init namedev on remove
Is there any reason to parse the rules for a remove event? Without it, our test script needs only 2.1 seconds instead of 2.5, so we have 19 percent more time for testing now :)
Diffstat (limited to 'udev.c')
-rw-r--r--udev.c21
1 files changed, 10 insertions, 11 deletions
diff --git a/udev.c b/udev.c
index d10badc8..1220e637 100644
--- a/udev.c
+++ b/udev.c
@@ -140,19 +140,18 @@ static int udev_hotplug(void)
sigaction(SIGINT, &act, NULL);
sigaction(SIGTERM, &act, NULL);
- /* initialize the naming deamon */
- namedev_init();
-
- if (strcmp(action, "add") == 0)
+ if (strcmp(action, "add") == 0) {
+ namedev_init();
retval = udev_add_device(devpath, subsystem, 0);
-
- else if (strcmp(action, "remove") == 0)
- retval = udev_remove_device(devpath, subsystem);
-
- else {
- dbg("unknown action '%s'", action);
- retval = -EINVAL;
+ } else {
+ if (strcmp(action, "remove") == 0) {
+ retval = udev_remove_device(devpath, subsystem);
+ } else {
+ dbg("unknown action '%s'", action);
+ retval = -EINVAL;
+ }
}
+
udevdb_exit();
exit_sysbus: