All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [RFC] kobject/kset/ktype documentation and example code updated
Date: Thu, 20 Dec 2007 14:20:04 -0800	[thread overview]
Message-ID: <20071220222004.GB16431@kroah.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712201659360.10061@localhost.localdomain>

On Thu, Dec 20, 2007 at 05:03:35PM -0500, Robert P. J. Day wrote:
> On Thu, 20 Dec 2007, Greg KH wrote:
> 
> > How about:
> > 	- A ktype is the type of object that embeds a kobject.
> 
> if i were reading the above for the first time, i would have no idea
> what was being embedded where.  "embeds a kobject" where?  what's
> being embedded in what?  that sentence doesn't make it clear.  what's
> the current definition for a "struct kobject"?

Read on and hopefully you will learn more.  As the beginning of the
article states, you have to start somewhere, it's all a circular
reference in the end :)

> >         Every structure that embeds a kobject needs a corresponding ktype.
> 
> and if it does, whose responsibility is it to provide one?  mine?
> that's not clear.

Well, someone has to provide it, the code will not compile without
one...

> > 	  The ktype controls what happens to the kobject when it is
> > 	  created and destroyed.
> 
> i doubt that.   i wouldn't say that the ktype "controls" what happens,
> i would say that it "defines" what happens.  to control suggests
> active participation.

Well, it controls how it is destroyed, and it controls how the uevents
happen when it is created.  It is quite active :)

thanks,

greg k-h

  reply	other threads:[~2007-12-20 22:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20  0:30 [RFC] kobject/kset/ktype documentation and example code updated Greg KH
2007-12-20  0:31 ` [RFC] sample kobject implementation code Greg KH
2007-12-20  0:31 ` [RFC] sample kset/ktype/kobject " Greg KH
2008-01-03 15:14   ` Cornelia Huck
2007-12-20  4:26 ` [RFC] kobject/kset/ktype documentation and example code updated Alan Stern
2007-12-20  7:27   ` Kay Sievers
2007-12-20 21:48   ` Greg KH
2007-12-20  6:32 ` Randy Dunlap
2007-12-20 21:27   ` Greg KH
2007-12-20 22:03     ` Robert P. J. Day
2007-12-20 22:20       ` Greg KH [this message]
2007-12-20 22:06     ` Randy Dunlap
2007-12-20 22:12       ` Greg KH
2007-12-20 22:29         ` Randy Dunlap
2007-12-20 22:42           ` Greg KH
2007-12-20 22:48             ` Randy Dunlap
2007-12-20 22:57     ` Alan Stern
2007-12-20  7:54 ` Dave Young
2007-12-20  8:02   ` Greg KH
2007-12-20  9:04 ` Jan Engelhardt
2007-12-20 21:16   ` 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=20071220222004.GB16431@kroah.com \
    --to=greg@kroah.com \
    --cc=corbet@lwn.net \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rpjday@crashcourse.ca \
    --cc=stern@rowland.harvard.edu \
    /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.