From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Date: Wed, 07 Nov 2007 05:52:36 +0000 Subject: Calling kobject_uevent directly Message-Id: <58b503a50711062152x3e3cedafxde62c964174a3e53@mail.gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org For devices with attributes that may change, is it "correct" to call kobject_uevent directly with KOBJ_CHANGE in order to notify userspace? (This appears to be the behavior used in the drivers/mmc/host/omap.c driver) The KOBJ_ADD and KOBJ_REMOVE actions have comments saying "exclusive to core". Is this policy or is there a technical reason? ------------------------------------------------------------------------- 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