From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Thu, 26 Jan 2006 01:57:33 +0000 Subject: Re: udev_rules_get_run confusion Message-Id: <20060126015733.GC1652@vrfy.org> List-Id: References: <200601252342.15059.arvidjaar@mail.ru> In-Reply-To: <200601252342.15059.arvidjaar@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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&kid3432&bid#0486&dat1642 _______________________________________________ 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