Lines Matching full:release

203 need to do a kobject_put() eventually to release that reference.
246 ktypes and release methods
268 This notification is done through a kobject's release() method. Usually
280 release() method, and the kobject must persist (in a consistent state)
283 release() method.  Do not try to get rid of this warning by providing an
284 "empty" release function.
291 Note, the name of the kobject is available in the release function, but it
295 Interestingly, the release() method is not stored in the kobject itself;
300             void (*release)(struct kobject *kobj);
313 The release field in struct kobj_type is, of course, a pointer to the
314 release() method for this type of kobject. The other two fields (sysfs_ops
365 Because other references to the kset may still exist, the release may happen
425 with an explicit call to kobject_del(), so that a release functions will be
426 called, and the objects in the former circle release each other.