Lines Matching refs:release

198 need to do a kobject_put() eventually to release that reference.
238 ktypes and release methods
259 This notification is done through a kobject's release() method. Usually
271 release() method, and the kobject must persist (in a consistent state)
274 release() method.  Do not try to get rid of this warning by providing an
275 "empty" release function; you will be mocked mercilessly by the kobject
278 Note, the name of the kobject is available in the release function, but it
282 Interestingly, the release() method is not stored in the kobject itself;
287 	    void (*release)(struct kobject *kobj);
299 The release field in struct kobj_type is, of course, a pointer to the
300 release() method for this type of kobject. The other two fields (sysfs_ops
347 Because other references to the kset may still exist, the release may happen
407 with an explicit call to kobject_del(), so that a release functions will be
408 called, and the objects in the former circle release each other.