From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Date: Wed, 07 Nov 2007 23:37:52 +0000 Subject: Re: Calling kobject_uevent directly Message-Id: <58b503a50711071537p7d0cf403h1b2e8f870d7bf2ef@mail.gmail.com> List-Id: References: <58b503a50711062152x3e3cedafxde62c964174a3e53@mail.gmail.com> In-Reply-To: <58b503a50711062152x3e3cedafxde62c964174a3e53@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org > Right, it's fine to send "change", you can also add additional keys to > the environment, > to make it easier for the possible consumer so determine what this > event is about. See: > drivers/acpi/dock.c::dock_event() Is there any advantage to sending the additional key directly with kobject_uevent_env() rather than just doing a kobject_uevent() call and using SYSFS{attribute}="some_value" in the udev rule? (e.g., perhaps it's faster?) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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