Lines Matching refs:reference

14 all of which make reference to each other. In an attempt to make things
20    and a reference count.  A kobject also has a parent pointer (allowing
29    If it does, the reference counting for the object is sure to be messed
184 One of the key functions of a kobject is to serve as a reference counter
187 The low-level functions for manipulating a kobject's reference counts are:
192 A successful call to kobject_get() will increment the kobject's reference
195 When a reference is released, the call to kobject_put() will decrement the
196 reference count and, possibly, free the object. Note that kobject_init()
197 sets the reference count to one, so the code which sets up the kobject will
198 need to do a kobject_put() eventually to release that reference.
205 If all that you want to use a kobject for is to provide a reference counter
241 kobject when its reference count reaches zero. The code which created the
245 in as other portions of the kernel can get a reference on any kobject that
249 before its reference count goes to zero. The reference count is not under
251 be notified asynchronously whenever the last reference to one of its
345 to destroy it.  This removes the kset from sysfs and decrements its reference
346 count.  When the reference count goes to zero, the kset will be released.
400 kobject "invisible", but it is not cleaned up, and the reference count of
404 kobject_del() can be used to drop the reference to the parent object, if