| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
32 Some regulator directories will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
196 Some regulator directories will contain a field called
234 Some regulator directories will contain a field called
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
32 Some regulator directories will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
196 Some regulator directories will contain a field called
234 Some regulator directories will contain a field called
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | autofs.rst | 45 An autofs filesystem can contain 3 sorts of objects: directories,
46 symbolic links and mount traps. Mount traps are directories with
50 created with a regular `symlink` system call, while directories and
53 map is consulted by autofs to determine which directories are mount
65 Directories created in the root directory are mount traps only if the
68 Directories further down the tree depend on the *maxproto* mount
70 When *maxproto* is five, no directories further down the
71 tree are ever mount traps, they are always regular directories. When
72 the *maxproto* is four (or three), these directories are mount traps
75 So: non-empty (i.e. non-leaf) directories are never mount traps. Empty
[all …]
|
| D | overlayfs.rst | 25 While directories will report an st_dev from the overlay-filesystem,
91 'lower' filesystem is either hidden or, in the case of directories,
109 Directories chapter
112 Overlaying mainly involves directories. If a given name appears in both
117 Where both upper and lower objects are directories, a merged directory
120 At mount time, the two directories given as mount options "lowerdir" and
132 actual lookups find directories, both are stored and a merged
136 Only the lists of names from directories are merged. Other content
140 whiteouts and opaque directories
146 directories (non-directories are always opaque).
[all …]
|
| D | squashfs.rst | 10 directories. Inodes in the system are very small and all blocks are packed to
33 Max directories unlimited unlimited
50 Squashfs compresses data, inodes and directories. In addition, inode and
115 Metadata (inodes and directories) are compressed in 8Kbyte blocks. Each
132 regular files and directories, and extended types where extra
135 3.3 Directories
138 Like inodes, directories are packed into compressed metadata blocks, stored
139 in a directory table. Directories are accessed using the start address of
143 Directories are organised in a slightly complex way, and are not simply
147 Directories are therefore organised in a two level list, a directory
[all …]
|
| D | directory-locking.rst | 31 non-directories - the source because it wouldn't be locked otherwise
57 * Lock non-directories involved, in inode pointer order.
62 The rules above obviously guarantee that all directories that are going to be
91 target in inode pointer order in the case they are not directories.)
143 not introduce a cycle will leave it a tree and link() fails for directories).
|
| D | omfs.rst | 12 block sizes from 2k to 8k, with hash-based directories. This
41 dmask=xxx set umask to xxx for directories
69 Files and directories are both represented by omfs_inode::
84 Directories in OMFS are implemented as a large hash table. Filenames are
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | autofs.rst | 45 An autofs filesystem can contain 3 sorts of objects: directories,
46 symbolic links and mount traps. Mount traps are directories with
50 created with a regular `symlink` system call, while directories and
53 map is consulted by autofs to determine which directories are mount
65 Directories created in the root directory are mount traps only if the
68 Directories further down the tree depend on the *maxproto* mount
70 When *maxproto* is five, no directories further down the
71 tree are ever mount traps, they are always regular directories. When
72 the *maxproto* is four (or three), these directories are mount traps
75 So: non-empty (i.e. non-leaf) directories are never mount traps. Empty
[all …]
|
| D | overlayfs.rst | 25 While directories will report an st_dev from the overlay-filesystem,
89 'lower' filesystem is either hidden or, in the case of directories,
109 Directories chapter
112 Overlaying mainly involves directories. If a given name appears in both
117 Where both upper and lower objects are directories, a merged directory
120 At mount time, the two directories given as mount options "lowerdir" and
132 actual lookups find directories, both are stored and a merged
136 Only the lists of names from directories are merged. Other content
140 whiteouts and opaque directories
146 directories (non-directories are always opaque).
[all …]
|
| D | squashfs.rst | 10 directories. Inodes in the system are very small and all blocks are packed to
33 Max directories unlimited unlimited
50 Squashfs compresses data, inodes and directories. In addition, inode and
115 Metadata (inodes and directories) are compressed in 8Kbyte blocks. Each
132 regular files and directories, and extended types where extra
135 3.3 Directories
138 Like inodes, directories are packed into compressed metadata blocks, stored
139 in a directory table. Directories are accessed using the start address of
143 Directories are organised in a slightly complex way, and are not simply
147 Directories are therefore organised in a two level list, a directory
[all …]
|
| D | ntfs3.rst | 56 - Controls the default permissions for files/directories created after
61 directories, fmask applies only to files and dmask only to directories.
79 - Prevents the creation of files and directories with a name not allowed
|
| D | directory-locking.rst | 31 non-directories - the source because it wouldn't be locked otherwise
57 * Lock non-directories involved, in inode pointer order.
62 The rules above obviously guarantee that all directories that are going to be
91 target in inode pointer order in the case they are not directories.)
143 not introduce a cycle will leave it a tree and link() fails for directories).
|
| D | omfs.rst | 12 block sizes from 2k to 8k, with hash-based directories. This
41 dmask=xxx set umask to xxx for directories
69 Files and directories are both represented by omfs_inode::
84 Directories in OMFS are implemented as a large hash table. Filenames are
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/samsung/ |
| D | overview.rst | 35 several platform directories and then the machine specific directories
39 last in the line of include directories that are processed for the build
51 The old plat-s3c and plat-s5pc1xx directories have been removed, with
54 so many different platform directories.
|
| /kernel/linux/linux-5.10/Documentation/arm/samsung/ |
| D | overview.rst | 46 several platform directories and then the machine specific directories
50 last in the line of include directories that are processed for the build
64 The old plat-s3c and plat-s5pc1xx directories have been removed, with
67 so many different platform directories.
|
| /kernel/linux/linux-5.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-plugins.txt | 27 directories. The _tep_ argument is trace event parser context.
28 The plugin directories are :
31 - Directories, specified in _tep_->plugins_dir with priority TEP_PLUGIN_FIRST
37 - Directories, specified in _tep_->plugins_dir with priority TEP_PLUGIN_LAST
55 The _tep_load_plugins_hook_ function walks through all directories with plugins
58 context, passed to _load_plugin()_. Directories and the walk order are the same
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 25 reading directories and opening the files yourself.
54 - all elements of a devpath must be real directories. Symlinks
105 It is planned that all device directories will end up in the tree
111 not contain any device directories themselves, but only flat lists of
115 classification directories into one place at ``/sys/subsystem``,
116 following the layout of the bus directories. All buses and
153 directory does not contain directories for child devices, these links
157 real child device directories in the ``/sys/devices`` tree is a bug in
161 directories live in ``/sys/devices.``
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 25 reading directories and opening the files yourself.
54 - all elements of a devpath must be real directories. Symlinks
105 It is planned that all device directories will end up in the tree
111 not contain any device directories themselves, but only flat lists of
115 classification directories into one place at ``/sys/subsystem``,
116 following the layout of the bus directories. All buses and
153 directory does not contain directories for child devices, these links
157 real child device directories in the ``/sys/devices`` tree is a bug in
161 directories live in ``/sys/devices.``
|
| /kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 154 Do not create, rename or unlink files and directories in the cache while the
163 Do not create files or directories in the cache, lest the cache get confused or
176 directories are culled if not in use.
213 The CacheFiles module will create two directories in the directory it was
227 The module represents index objects as directories with the filename "I..." or
230 Data objects are represented as files if they have no children, or directories
240 Immediately in the representative directory are a collection of directories
255 make a nest of directories, and the last one of which will be the objects
256 inside the last directory. The names of the intermediate directories will have
278 Intermediate directories are always "@" or "+" as appropriate.
[all …]
|
| /kernel/linux/linux-6.6/fs/squashfs/ |
| D | namei.c | 12 * This file implements code to do filename lookup in directories.
14 * Like inodes, directories are packed into compressed metadata blocks, stored
15 * in a directory table. Directories are accessed using the start address of
19 * Directories are organised in a slightly complex way, and are not simply
23 * Directories are therefore organised in a two level list, a directory
29 * Directories are sorted, and can contain a directory index to speed up
32 * in each metadata block. Directories are sorted in alphabetical order,
|
| /kernel/linux/linux-5.10/fs/squashfs/ |
| D | namei.c | 12 * This file implements code to do filename lookup in directories.
14 * Like inodes, directories are packed into compressed metadata blocks, stored
15 * in a directory table. Directories are accessed using the start address of
19 * Directories are organised in a slightly complex way, and are not simply
23 * Directories are therefore organised in a two level list, a directory
29 * Directories are sorted, and can contain a directory index to speed up
32 * in each metadata block. Directories are sorted in alphabetical order,
|
| /kernel/linux/linux-6.6/fs/hmdfs/ |
| D | Kconfig | 7 the shared directories of the corresponding devices are provided under
8 different device directories; in the merge view, acollection of shared
16 application can access the files and directories under the corresponding
|
| /kernel/linux/linux-5.10/fs/hmdfs/ |
| D | Kconfig | 7 the shared directories of the corresponding devices are provided under
8 different device directories; in the merge view, acollection of shared
16 application can access the files and directories under the corresponding
|
| /kernel/linux/linux-6.6/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 155 Do not create, rename or unlink files and directories in the cache while the
164 Do not create files or directories in the cache, lest the cache get confused or
177 directories are culled if not in use.
214 The CacheFiles module will create two directories in the directory it was
228 The module represents index objects as directories with the filename "I..." or
231 Data objects are represented as files if they have no children, or directories
241 Immediately in the representative directory are a collection of directories
256 make a nest of directories, and the last one of which will be the objects
257 inside the last directory. The names of the intermediate directories will have
279 Intermediate directories are always "@" or "+" as appropriate.
[all …]
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | landlock.h | 94 * files and directories. Files or directories opened before the sandboxing
114 * A directory can receive access rights related to files or directories. The
116 * directories beneath it:
146 * always deny attempts to reparent files between different directories.
148 * In addition to the source and destination directories having the
|