From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: who sends from the kernel an event to udevd netlink socket?
Date: Mon, 27 Mar 2006 14:07:23 +0000 [thread overview]
Message-ID: <20060327140723.GB13507@vrfy.org> (raw)
In-Reply-To: <dac45060603270310m6c5e91b2o2bfbc2ba75d66cd4@mail.gmail.com>
On Mon, Mar 27, 2006 at 03:13:05PM +0200, Mark Ryden wrote:
> Thanks,
> Last question on this, to verify I understand correctly, if I may:
> class_device_add() in class.c calls kobject_hotplug().
> kobject_hotplug() calls send_uevent() which calls netlink_broadcast();
> this is true only if CONFIG_HOTPLUG is defined,because
> if it is not defined kobject_hotplug() is an empty function. (see the
> header file ,
> kobject.h)
>
> So, as I understand, CONFIG_HOTPLUG must be defined (even though in
> fact we don't use hotplug itself) in order that uevents will be sent via netlink
> to the udev user space daemon.
Yes, but CONFIG_HOTPLUG depends on CONFIG_EMBEDDED, so you usually
can't disable it for a "normal" kernel.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&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
prev parent reply other threads:[~2006-03-27 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 11:10 who sends from the kernel an event to udevd netlink socket? Mark Ryden
2006-03-27 11:30 ` Kay Sievers
2006-03-27 13:13 ` Mark Ryden
2006-03-27 14:07 ` Kay Sievers [this message]
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=20060327140723.GB13507@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).