Lines Matching refs:A

27 A configfs config_item is created via an explicit userspace operation:
82 A fakenbd connection can be created with mkdir(2).  The name is
104 Every object in configfs is a config_item.  A config_item reflects an
110 Items are created and destroyed inside a config_group.  A group is a
115 A subsystem is the top level of a client module.  During initialization,
117 appears as a directory at the top of the configfs filesystem.  A
206 A config_item cannot live in a vacuum.  The only way one can be created
241 A group creates child items by providing the
277 A config_group cannot be removed while it still has child items.  This
284 A subsystem must register itself, usually at module_init time.  This
295 	A subsystem consists of a toplevel config_group and a mutex.
317 appear in a filesystem.  A subsystem is NEVER to touch the filesystem
322 A subsystem can navigate the cg_children list and the ci_parent pointer
329 A subsystem will be prevented from acquiring the mutex while a newly
345 A config_item may provide the ct_item_ops->allow_link() and
353 allows linking to target item, it returns 0.  A source item may wish to
362 A config_item cannot be removed while it links to any other item, nor
368 A new config_group may want to have two types of child config_items.
384 A configfs subsystem specifies default groups by filling in the
404 configfs_undepend_item().  A client driver can call
411 they will conflict.  They can block and allocate.  A client driver