Lines Matching refs:code

26    the code is really interested in.
30    up and incorrect, and your code will be buggy.  So do not do this.
39    safely ignore that implementation detail as the kset core code handles
52 It is rare for kernel code to create a standalone kobject, with one major
68 So, for example, the UIO code in ``drivers/uio/uio.c`` has a structure that
148 is being removed.  If your code needs to call this function, it is
191 exist, the object (and the code which supports it) must continue to exist.
202 sets the reference count to one, so the code which sets up the kobject will
250 kobject when its reference count reaches zero. The code which created the
259 the direct control of the code which created the kobject. So that code must
281 until that method is called. If these constraints are not met, the code is
343 contain their own kobject, but that kobject is managed by the kset code and
409 must be cleaned up when the code is finished with it.  To do that, call
429 Example code to copy from