public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ikke <ikke.lkml@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kobject_uevent
Date: Fri, 7 Jan 2005 16:14:07 +0100	[thread overview]
Message-ID: <297f4e0105010707142be80168@mail.gmail.com> (raw)
In-Reply-To: <297f4e01050107065060e0b2ad@mail.gmail.com>

Next to this, there seems to be a mistake in the 2.6.10 changelog: it writes
[quote]
kobject_uevent(const char *signal,
	                 struct kobject *kobj,
	                 struct attribute *attr)
[/quote]
whilst include/linux/kobject_uevent.h defines
[quote]
int kobject_uevent(struct kobject *kobj,
                   enum kobject_action action,
                   struct attribute *attr);
[/quote]
which is something completely different.

On Fri, 7 Jan 2005 15:50:52 +0100, Ikke <ikke.lkml@gmail.com> wrote:
> One of the new features of 2.6.10 (well, AFAIK its new) is the
> kobject_uevent function set.
> Currently only some places send out events like this, so I was
> thinking to add some more.
> 
> Question is: how can I test this? Is there any userland program that
> catches these events and prints some information on them to the
> screen?
> 
> I found out Kay Siever and RML's (maybe some others too?) work on
> kernel->userspace events, but the syntax used there seems to be
> somewhat different. Kay's got a listener
> (http://vrfy.org/projects/kdbusd/kdbusd.c), but is this one
> compatible?
> 
> Regards, Ikke
>

  reply	other threads:[~2005-01-07 15:14 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 ` Ikke [this message]
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     ` 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=297f4e0105010707142be80168@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