From: Greg KH <greg@kroah.com>
To: Ikke <ikke.lkml@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kobject_uevent
Date: Fri, 7 Jan 2005 09:39:16 -0800 [thread overview]
Message-ID: <20050107173916.GB15417@kroah.com> (raw)
In-Reply-To: <297f4e0105010707142be80168@mail.gmail.com>
On Fri, Jan 07, 2005 at 04:14:07PM +0100, Ikke wrote:
> 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.
Look further on in the changelog where I changed the api to the current
one :)
thanks,
greg k-h
next prev parent reply other threads:[~2005-01-07 17:39 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 ` Greg KH [this message]
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=20050107173916.GB15417@kroah.com \
--to=greg@kroah.com \
--cc=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