From: Ikke <ikke.lkml@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kobject_uevent
Date: Fri, 7 Jan 2005 22:25:14 +0100 [thread overview]
Message-ID: <297f4e0105010713254b6e0678@mail.gmail.com> (raw)
In-Reply-To: <297f4e01050107065060e0b2ad@mail.gmail.com>
I've been working a bit on the kobject_uevent stuff, and got a
prototype system working (well, almost) which takes kernel's uevents,
and sends them to the DBUS system bus so other software can (ab)use
them.
I'll add more uevents later, once I understand the system completely.
I'm a little confused by the use of KOBJ_* stuff in
include/linux/kobject_uevent.h and the string representation of them
in lib/kobject_uevent.c, which means people must edit 2 files if they
want to add new events?
More information on my little work here [1]
Regards, Ikke
[1] http://blog.eikke.com/index.php/ikke/2005/01/07/kernel_events_to_dbus
next prev parent reply other threads:[~2005-01-07 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 14:50 kobject_uevent Ikke
2005-01-07 15:14 ` kobject_uevent Ikke
2005-01-07 16:55 ` kobject_uevent Robert Love
2005-01-07 17:39 ` kobject_uevent Greg KH
2005-01-07 17:38 ` kobject_uevent Greg KH
2005-01-07 21:25 ` Ikke [this message]
2005-01-07 23:36 ` kobject_uevent Greg KH
2005-01-08 9:56 ` kobject_uevent Ikke
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=297f4e0105010713254b6e0678@mail.gmail.com \
--to=ikke.lkml@gmail.com \
--cc=linux-kernel@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