Messages in this thread | | | Date | Thu, 29 Nov 2007 18:52:17 +0100 | From | Cornelia Huck <> | Subject | Re: [RFC] New kobject/kset/ktype documentation and example code |
| |
On Thu, 29 Nov 2007 11:55:43 -0500 (EST), Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 29 Nov 2007, Cornelia Huck wrote: > > > > Unfortunately kobjects don't have an owner field. In practice this > > > means that it isn't possible to pin the owner of some random kobject -- > > > you have to know where the kobject came from or what it's embedded in. > > > All users of kobjects need to work this way. > > > > Yeah, that is what the-patchset-I-have-to-dig-around-for does: > > Introduce an owner field in the kobject for pinning the module. (IIRC, > > you even did some of the patches?) > > Are these two patches what you mean? They are a little out-of-date > now, but the main idea hasn't changed.
Yes, thanks. I had also a module-reference-count part that I need to resurrect. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |