Lines Matching refs:must

60 embedding - must be used.
78 what is the pointer to the containing structure?  You must avoid tricks
116 Code which creates a kobject must, of course, initialize that object. Some
122 must have an associated kobj_type.  After calling kobject_init(), to
123 register the kobject with sysfs, the function kobject_add() must be called:
129 kobj->kset must be assigned before calling kobject_add().  If a kset is
135 of the kobject should never be manipulated directly.  If you must change
141 what names are valid so the caller must provide their own sanity checking
186 exist, the object (and the code which supports it) must continue to exist.
200 Because kobjects are dynamic, they must not be declared statically or on
250 the direct control of the code which created the kobject. So that code must
254 Once you registered your kobject via kobject_add(), you must never use
270 One important point cannot be overstated: every kobject must have a
271 release() method, and the kobject must persist (in a consistent state)
279 must NOT be changed within this callback.  Otherwise there will be a memory
296 kobj_type structure; a pointer to that structure must be specified when you
391 must be cleaned up when the code is finished with it.  To do that, call