mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
	mochel@osdl.org, linux-kernel@vger.kernel.org,
	Greg KH <gregkh@suse.de>
Subject: Re: [PATCH] Fix kobject documentation
Date: Fri, 27 Jul 2007 09:36:26 -0700	[thread overview]
Message-ID: <20070727093626.76d0c56f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070727132115.45b70a5e@gondolin.boeblingen.de.ibm.com>

On Fri, 27 Jul 2007 13:21:15 +0200 Cornelia Huck wrote:

> On Fri, 27 Jul 2007 19:27:26 +0900,
> Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com> wrote:
> 
> > Fix kobject documentation as follows.
> > 
> >  - remove trailing spaces.
> >  - struct device_subsys -> devices_subsys
> > 
> > Signed-off-by: Satoru Takeuchi<takeuchi_satoru@jp.fujitsu.com>
> 
> This is certainly a start, but kobject.txt needs more updates. For
> example, it still refers to the removed struct subsystem, and
> uevent_ops are not mentioned. Looking at kobject.h, the kerneldoc there
> needs some updates as well...

Here's a start at that.
---


From: Randy Dunlap <randy.dunlap@oracle.com>

Removed kernel-doc marker (/**) from struct kset -- each struct member
still needs annotation.

Corrected one parameter name so that kernel-doc matches the macro.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 include/linux/kobject.h |   23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

--- linux-2623-rc1g2.orig/include/linux/kobject.h
+++ linux-2623-rc1g2/include/linux/kobject.h
@@ -108,9 +108,15 @@ struct kobj_type {
 	struct attribute	** default_attrs;
 };
 
+struct kset_uevent_ops {
+	int (*filter)(struct kset *kset, struct kobject *kobj);
+	const char *(*name)(struct kset *kset, struct kobject *kobj);
+	int (*uevent)(struct kset *kset, struct kobject *kobj, char **envp,
+			int num_envp, char *buffer, int buffer_size);
+};
 
-/**
- *	kset - a set of kobjects of a specific type, belonging
+/*
+ *	struct kset - a set of kobjects of a specific type, belonging
  *	to a specific subsystem.
  *
  *	All kobjects of a kset should be embedded in an identical 
@@ -126,13 +132,6 @@ struct kobj_type {
  *	supress the event generation or add subsystem specific
  *	variables carried with the event.
  */
-struct kset_uevent_ops {
-	int (*filter)(struct kset *kset, struct kobject *kobj);
-	const char *(*name)(struct kset *kset, struct kobject *kobj);
-	int (*uevent)(struct kset *kset, struct kobject *kobj, char **envp,
-			int num_envp, char *buffer, int buffer_size);
-};
-
 struct kset {
 	struct kobj_type	* ktype;
 	struct list_head	list;
@@ -173,7 +172,7 @@ static inline struct kobj_type * get_kty
 extern struct kobject * kset_find_obj(struct kset *, const char *);
 
 
-/**
+/*
  * Use this when initializing an embedded kset with no other 
  * fields to initialize.
  */
@@ -198,7 +197,7 @@ extern struct kset kernel_subsys;
 /* The global /sys/hypervisor/ subsystem  */
 extern struct kset hypervisor_subsys;
 
-/**
+/*
  * Helpers for setting the kset of registered objects.
  * Often, a registered object belongs to a kset embedded in a 
  * subsystem. These do no magic, just make the resulting code
@@ -233,7 +232,7 @@ extern struct kset hypervisor_subsys;
 /**
  *	subsys_set_kset(obj,subsys) - set kset for subsystem
  *	@obj:		ptr to some object type.
- *	@subsys:	a subsystem object (not a ptr).
+ *	@_subsys:	a subsystem object (not a ptr).
  *
  *	Can be used for any object type with an embedded ->subsys.
  *	Sets the kset of @obj's kobject to @subsys.kset. This makes

      parent reply	other threads:[~2007-07-27 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 10:27 Satoru Takeuchi
2007-07-27 11:21 ` Cornelia Huck
2007-07-27 11:41   ` Cornelia Huck
2007-07-27 16:36   ` Randy Dunlap [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=20070727093626.76d0c56f.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=takeuchi_satoru@jp.fujitsu.com \
    /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

all inboxes | Powered by JetHome®