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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
