From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Calling kobject_uevent directly
Date: Wed, 07 Nov 2007 06:53:39 +0000 [thread overview]
Message-ID: <20071107065339.GA22201@kroah.com> (raw)
In-Reply-To: <58b503a50711062152x3e3cedafxde62c964174a3e53@mail.gmail.com>
On Tue, Nov 06, 2007 at 09:52:36PM -0800, Tom wrote:
> For devices with attributes that may change, is it "correct" to call
> kobject_uevent directly with KOBJ_CHANGE in order to notify userspace?
Yes. And what attribute do you want to do this for?
> (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?
Both. lots of userspace stuff happens when these events are sent, so
don't be sending them unless you really think you know what you are
doing. And even then, please run the kernel patch by me and Kay to
ensure that nothing bad will happen.
Do you have a reason why you would want to do this?
thanks,
greg k-h
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-11-07 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 5:52 Calling kobject_uevent directly Tom
2007-11-07 6:53 ` Greg KH [this message]
2007-11-07 11:17 ` Kay Sievers
2007-11-07 23:37 ` Tom
2007-11-08 0:07 ` Kay Sievers
2007-11-08 22:35 ` Tom
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=20071107065339.GA22201@kroah.com \
--to=greg@kroah.com \
--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).