From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev_rules_get_run confusion
Date: Thu, 26 Jan 2006 01:57:33 +0000 [thread overview]
Message-ID: <20060126015733.GC1652@vrfy.org> (raw)
In-Reply-To: <200601252342.15059.arvidjaar@mail.ru>
On Wed, Jan 25, 2006 at 11:42:14PM +0300, Andrey Borzenkov wrote:
> What this function does? As it is now it does *not* get called at all.
$ grep udev_rules_get_run *
udev_device.c: udev_rules_get_run(rules, udev);
udev_device.c: udev_rules_get_run(rules, udev);
udev_rules.c:int udev_rules_get_run(struct udev_rules *rules, struct udevice *udev)
udev_rules.h:extern int udev_rules_get_run(struct udev_rules *rules, struct udevice *udev);
> Is it leftover from the past or something for the future?
It is called for all events, that don't create a node and need to "name"
a device. The logic is a bit different, if NAME is contained in a rule, that's
why they are different functions. udev_rules_get_name() and udev_rules_get_run()
could be merged, sure, if it would improve something, but I'm not sure about.
Thanks,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-01-26 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 20:42 udev_rules_get_run confusion Andrey Borzenkov
2006-01-26 1:57 ` Kay Sievers [this message]
2006-01-26 17:40 ` Andrey Borzenkov
2006-01-26 23:12 ` Kay Sievers
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=20060126015733.GC1652@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).