Lines Matching refs:be

11 to be maintained forever.
20 options can be used.
25 of business will be to create at least one directory to hold a set of
31 indicated parent directory.  If parent is NULL, the directory will be
33 dentry pointer which can be used to create files in the directory (and to
47 should hold the file, data will be stored in the i_private field of the
50 operations should be provided; others can be included as needed.  Again,
51 the return value will be a dentry pointer to the created file, NULL for
54 Create a file with an initial size, the following function can be used
67 for simple situations.  Files containing a single integer value can be
80 file should not be written to, simply set the mode bits accordingly.  The
82 the following functions can be used instead:
94 value to be exported.  Some types can have different widths on different
102 As might be expected, this function will create a debugfs file to represent
105 Boolean values can be placed in debugfs with:
112 lower-case values, or 1 or 0.  Any other input will be silently ignored.
114 Also, atomic_t values can be placed in debugfs with:
137 can be used to export binary information, but there does not appear to be
165 The "base" argument may be 0, but you may want to build the reg32 array
177 size can not be changed.
188 the "read_fn" is a function pointer which to be called to print the
205 Symbolic links can be created with debugfs_create_symlink().
210 will be a lot of stale pointers and no end of highly antisocial behavior.
211 So all debugfs users - at least those which can be built as modules - must
212 be prepared to remove all files and directories they create there.  A file
213 can be removed with:
217 The dentry value can be NULL, in which case nothing will be removed.
220 pointer for every debugfs file they created so that all files could be
227 top-level directory, the entire hierarchy below that directory will be