All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] Driver Core: restore comment in kobject_uevent.c
Date: Fri, 3 Dec 2004 12:00:04 -0800	[thread overview]
Message-ID: <20041203200003.GB1178@kroah.com> (raw)
In-Reply-To: <20041203195908.GA1178@kroah.com>

Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

--- 1.6/drivers/base/class_simple.c	2004-06-10 08:34:24 +02:00
+++ edited/drivers/base/class_simple.c	2004-11-26 20:11:21 +01:00
@@ -122,7 +122,7 @@ EXPORT_SYMBOL(class_simple_destroy);
  * be created, showing the dev_t for the device.  The pointer to the struct
  * class_device will be returned from the call.  Any further sysfs files that
  * might be required can be created using this pointer.
- * Note: the struct class_device passed to this function must have previously been
+ * Note: the struct class_simple passed to this function must have previously been
  * created with a call to class_simple_create().
  */
 struct class_device *class_simple_device_add(struct class_simple *cs, dev_t dev, struct device *device, const char *fmt, ...)
===== lib/kobject_uevent.c 1.16 vs edited =====
--- 1.16/lib/kobject_uevent.c	2004-11-12 12:50:24 +01:00
+++ edited/lib/kobject_uevent.c	2004-11-26 20:19:53 +01:00
@@ -205,6 +205,8 @@ void kobject_hotplug(struct kobject *kob
 	static struct kset_hotplug_ops null_hotplug_ops;
 	struct kset_hotplug_ops *hotplug_ops = &null_hotplug_ops;
 
+	/* If this kobj does not belong to a kset,
+	   try to find a parent that does. */
 	if (!top_kobj->kset && top_kobj->parent) {
 		do {
 			top_kobj = top_kobj->parent;



  reply	other threads:[~2004-12-03 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 19:59 [PATCH 0/3] A few misc patches for 2.6.10-rc2 Greg KH
2004-12-03 20:00 ` Greg KH [this message]
2004-12-03 20:00   ` [PATCH 2/3] sysfs: fix sysfs_dir_close memory leak Greg KH
2004-12-03 20:01     ` [PATCH 3/3] Add documentation about why the in-kernel api is the way it is Greg KH

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=20041203200003.GB1178@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.