public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ikke <ikke.lkml@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kobject_uevent
Date: Sat, 8 Jan 2005 10:56:49 +0100	[thread overview]
Message-ID: <297f4e010501080156736e929e@mail.gmail.com> (raw)
In-Reply-To: <20050107233632.GA1467@kroah.com>

Ok, events are sent to DBUS now, including the additional string
information [1]. Code (for now, it's not "done" yet!) is here [2].

I'll ask the DBUS guys whether it's usefull to get this (optionally)
directly into DBUS.

Let's hope other kernel devs will also start introducing events into
their code! :-)

Greetings, Ikke

[1] http://blog.eikke.com/index.php/ikke/2005/01/08/udev_kernel_events_part_2
[2] http://www.eikke.com/files/code/uevent_listen.c


On Fri, 7 Jan 2005 15:36:32 -0800, Greg KH <greg@kroah.com> wrote:
> On Fri, Jan 07, 2005 at 10:25:14PM +0100, Ikke wrote:
> > 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?
> 
> Yes, that is exactly correct.  The enumerated type is used for the
> callers to kobject_uevent* and the string is sent out on the wire from
> within the kevent core code.
> 
> Hope this helps,
> 
> greg k-h
>

      reply	other threads:[~2005-01-08 10:00 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 ` kobject_uevent Ikke
2005-01-07 23:36   ` kobject_uevent Greg KH
2005-01-08  9:56     ` Ikke [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=297f4e010501080156736e929e@mail.gmail.com \
    --to=ikke.lkml@gmail.com \
    --cc=greg@kroah.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