Home
last modified time | relevance | path

Searched refs:directory (Results 1 – 200 of 689) sorted by relevance

1234

/linux-4.1.27/Documentation/filesystems/
Ddirectory-locking1 Locking scheme used for directory operations is based on two
5 When taking the i_mutex on multiple non-directory objects, we
11 1) read access. Locking rules: caller locks directory we are accessing.
18 4) rename() that is _not_ cross-directory. Locking rules: caller locks
20 it. If source is a non-directory, lock it. If that means we need to
25 * check that source is not a directory
29 6) cross-directory rename. The trickiest in the whole bunch. Locking
38 * If target exists, lock it. If source is a non-directory, lock
48 If no directory is its own ancestor, the scheme above is deadlock-free.
56 (1) if object removal or non-cross-directory rename holds lock on A and
[all …]
Ddnotify.txt6 The intention of directory notification is to allow user applications
7 to be notified when a directory, or any of the files in it, are changed.
9 on a directory using a fcntl(2) call and the notifications themselves
15 DN_ACCESS A file in the directory was accessed (read)
16 DN_MODIFY A file in the directory was modified (write,truncate)
17 DN_CREATE A file was created in the directory
18 DN_DELETE A file was unlinked from directory
19 DN_RENAME A file in the directory was renamed
20 DN_ATTRIB A file in the directory had its attributes
31 file descriptor associated with the directory in which the event occurred.
[all …]
Doverlayfs.txt23 all non-directory objects will report an st_dev from the lower or
26 over the lifetime of a non-directory object. Many applications and
38 It would be more correct to refer to an upper and lower 'directory
40 directory trees to be in the same filesystem and there is no
57 upper and lower filesystems and refers to a non-directory in either,
61 Where both upper and lower objects are directories, a merged directory
65 "upperdir" are combined into a merged directory:
70 The "workdir" needs to be an empty directory on the same filesystem
73 Then whenever a lookup is requested in such a merged directory, the
74 lookup is performed in each actual directory and the combined result
[all …]
Dvfat.txt20 dmask=### -- The permission mask for the directory.
32 The default is set from `dmask' option. (If the directory is
78 currently exist in the directory, 'longfile.txt' will
137 the ATTR_RO of the directory will just be ignored,
142 the directory, set this option.
157 stale_rw: This option maintains an index (cache) of directory
164 on the on-disk location of a file in the MS-DOS directory entry.
186 a get next directory entry approach. The only thing left that uses
187 raw scanning is the directory renaming code.
193 * When a volume name is the same as a directory name in the root
[all …]
Dsquashfs.txt29 Max entries per directory: unlimited unlimited
45 directory data are highly compacted, and packed on byte boundaries. Each
47 file type, i.e. regular file, directory, symbolic link, and block/char device
78 | directory |
95 the source directory, and checked for duplicates. Once all file data has been
96 written the completed inode, directory, fragment, export, uid/gid lookup and
121 (regular file, directory, device, etc.), the inode contents and length
125 directory inode are defined: inodes optimised for frequently occurring
133 in a directory table. Directories are accessed using the start address of
134 the metablock containing the directory and the offset into the
[all …]
Dsysfs-tagging.txt9 the same directory, ouch!
13 sysfs, sysfs now has tagging directory support.
16 the sysfs directory entries we ensure that we don't have conflicts
20 Each sysfs directory entry may be tagged with zero or one
22 directory entry is tagged, then sysfs_dirent->s_flags will have a
Ddebugfs.txt18 The debugfs root directory is accessible only to the root user by
25 of business will be to create at least one directory to hold a set of
30 This call, if successful, will make a directory called name underneath the
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
39 The most general way to create a file within a debugfs directory is with:
46 permissions the file should have, parent indicates the directory which
151 There are a couple of other directory-oriented helper functions:
163 file, possibly in a different directory. The new_name must not exist prior
187 top-level directory, the entire hierarchy below that directory will be
Dsysfs.txt35 For every kobject that is registered with the system, a directory is
36 created for it in sysfs. That directory is created as a subdirectory
43 directory in the sysfs_dirent object associated with the directory. In
255 The sysfs directory arrangement exposes the relationship of kernel
258 The top level sysfs directory looks like:
273 bus/ contains flat directory layout of the various bus types in the
274 kernel. Each bus's directory contains two subdirectories:
280 that point to the device's directory under root/.
282 drivers/ contains a directory for each device driver that is loaded
286 fs/ contains a directory for some filesystems. Currently each
[all …]
D00-INDEX26 - directory containing filesystem cache documentation.
30 - directory containing CIFS filesystem documentation and example code.
34 - directory containing configfs documentation and example code.
44 directory-locking
45 - info about the locking scheme used for directory operations.
49 - info about directory notification in Linux.
111 - directory containing pohmelfs filesystem documentation.
Dhpfs.txt98 moved ... sometimes it works. But the link is partly stored in directory
115 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
117 (note, that files in HPFS directory must be sorted) and when searching for
118 a file. Finally when I opened this directory in PmShell, PmShell crashed (the
119 funny thing was that, when rebooted, PmShell tried to reopen this directory
147 (returning error ENOSPC). That's because file in non-leaf node in directory tree
148 (one directory, if it's large, has dirents in tree on HPFS) must be replaced
150 the old one so the new name doesn't fit in directory node (dnode). And that
151 would result in directory tree splitting, that takes disk space. Workaround is
155 preallocated directory band is full i.e.
[all …]
Dxfs.txt77 directory in which it is created; otherwise it takes the
78 fsgid of the current process, unless the directory has the
80 parent directory, and also gets the setgid bit set if it is
81 a directory itself.
308 by the xfs_io(8) chattr command on a directory to be
309 inherited by files in that directory.
313 by the xfs_io(8) chattr command on a directory to be
314 inherited by files in that directory.
318 by the xfs_io(8) chattr command on a directory to be
319 inherited by files in that directory.
[all …]
Dceph.txt18 * Flexible snapshots (on any directory)
59 files and bytes. That is, a 'getfattr -d foo' on any directory in the
109 When stat() is called on a directory, set st_size to 'rbytes',
111 directory. This is the default.
114 When stat() is called on a directory, set st_size to the
115 number of entries in that directory.
124 readdir when the client has the entire directory contents in
Daffs.txt20 DOS\4 The original filesystem with directory cache. The directory
21 cache speeds up directory accesses on floppies considerably,
25 DOS\5 The Fast File System with directory cache. Supported read only.
106 they will be owned by root. The root directory (the mount point) of the
108 filesystem (the root directory doesn't have uid/gid fields).
132 root directory, the Amiga has a separate root directory for each
136 different volume. AFFS turns the volume name into a directory name
Dqnx6.txt96 A directory is a filesystem object and has an inode just like a file.
99 '.' inode number points to the directory inode
100 '..' inode number points to the parent directory inode
104 These got set a filename length field of 0xff in the corresponding directory
114 The directory entry file inode pointer points to the target file inode.
116 Hard links got an inode, a directory entry, but a specific mode bit set,
117 no block pointers and the directory file record pointing to the target file
Decryptfs.txt38 Create a new directory into which eCryptfs will write its encrypted
39 files (i.e., /root/crypt). Then, create the mount point directory
69 mount a directory that has pre-existing files not created by eCryptfs,
Dext2.txt146 directory ACL if the inode is a directory and alternately for the top 32
172 A directory is a filesystem object and has an inode just like a file.
175 encode the type of the object (file, directory, symlink, device, fifo,
181 block group as the directory in which they are first created.
184 the filenames in the directory; a pending enhancement uses hashing of the
185 filenames to allow lookup without the need to scan the entire directory.
187 The current implementation never removes empty directory blocks once they
265 than 256 characters, which would lead to corrupt directory listings.
326 There is an upper limit of 32000 subdirectories in a single directory.
328 There is a "soft" upper limit of about 10-15k files in a single directory
[all …]
Dexofs.txt36 [parent-directory]$ git clone git://git.open-osd.org/open-osd.git
39 [parent-directory]$ make -C KSRC=$(KER_DIR) open-osd
53 4. Make sure the directory where you want to mount exists. If not, create it.
102 mount_exofs_directory: The directory to mount the file system on
135 * A directory is treated as a file, and essentially contains a list of <file
136 name, inode #> pairs for files that are found in that directory. The object
Dramfs-rootfs-initramfs.txt102 linked into the linux kernel image. (The directory linux-*/usr is devoted
141 archive, a directory containing files to be archived, or a text file
161 a directory called "initramfs", under the linux-2.6.* directory. See
165 directory instead of a configuration file, the kernel's build infrastructure
166 creates a configuration file from that directory (usr/Makefile calls
167 scripts/gen_initramfs_list.sh), and proceeds to package up that directory
175 (instead of a config file or directory).
192 echo "usage: mkinitramfs directory imagename.cpio.gz"
201 echo "First argument must be a directory"
210 work. The Linux kernel cpio extractor won't create files in a directory that
[all …]
Dudf.txt28 dmode= Set the default directory permissions.
69 rootdir= Override the root directory location. (unused)
70 WARNING: overriding the rootdir to a non-directory may
Dlogfs.txt55 Objects are either inodes, directory entries (dentries), file data
139 parent directory.
175 To satisfy efficient lookup(), directory entries are hashed and
195 10,000 runs the lowest directory fill before a bucket overflow was
197 directory sizes of up to a million, bucket overflows should be
203 to a directory.
Dcoda.txt445 directory in the Coda filesystem within a _c_e_l_l. (-- A _c_e_l_l is a
581 SSuummmmaarryy Find the ViceFid and type of an object in a directory if it
605 a directory entry. The directory entry requested carries name name
606 and Venus will search the directory identified by cfs_lookup_in.VFid.
760 The file will be created in the directory identified by VFid, its name
784 The attributes of the directory should be returned too, since the size
792 SSuummmmaarryy Create a new directory.
816 DDeessccrriippttiioonn This call is similar to create but creates a directory.
819 the new directory.
851 DDeessccrriippttiioonn This call creates a link to the sourceFid in the directory
[all …]
Df2fs.txt128 directory entries can be written into inode block. The
167 /sys/fs/f2fs. Each mounted filesystem will have a directory in
169 The files in each per-device directory are shown in table below.
235 dir_level This parameter controls the directory level to
236 support large directory. If a directory has a
256 3. Create a directory trying to mount
369 : It contains file and directory data including their indices.
437 A directory entry occupies 11 bytes, which consists of the following attributes.
442 - type file type such as directory, symlink, etc
469 F2FS implements multi-level hash tables for directory structure. Each level has
[all …]
Dntfs.txt89 since to mark a file sparse we need to modify the directory entry for the
90 file and we do not implement directory modifications yet.
97 files, since to mark a file sparse we need to modify the directory entry for
98 the file and we do not implement directory modifications yet.
148 in directory listings. Otherwise the default behaviour
216 - The link count on each directory inode entry is set to 1, due to Linux not
217 supporting directory hard links. This may well confuse some user space
218 applications, since the directory names will have the same inode numbers.
276 into it (cd linux-ldm-0.0.8) and change to the test directory (cd test). You
368 (You need to create the directory /mnt/myvol1 first and of course you can use
[all …]
/linux-4.1.27/Documentation/
D00-INDEX33 - directory with DocBook templates etc. for kernel documentation.
35 - directory with info on customizing EDID for broken gfx/displays.
53 - directory with info on RCU (read-copy update).
77 - directory with info about Linux on the ARM architecture.
79 - directory with info about Linux on the 64 bit ARM architecture.
87 - directory with info on controlling backlights in flat panel displays
97 - directory with documentation for the Blackfin arch.
109 - directory with info on TI GPMC (General Purpose Memory Controller)
115 - directory with information on the CD-ROM drivers that Linux has.
141 - directory with info about Linux on CRIS architecture.
[all …]
Dgcov.txt20 is exported in gcov-compatible format via the "gcov" debugfs directory.
22 directory and use gcov with the -o option as follows (requires root):
28 in the current directory. In addition, graphical gcov front-ends such
80 For all files in one directory:
100 Parent directory for all gcov-related files.
160 directory needs to be used instead (due to make's CURDIR handling).
167 from the gcov directory in sysfs:
172 must then be called with the -o option pointing to that directory.
174 Example directory setup on the build machine:
177 /tmp/out: kernel build directory as specified by make O=
[all …]
Dinitrd.txt12 to a directory and can be subsequently unmounted.
39 7) init places the root file system at the root directory using the
45 Note that changing the root directory does not involve unmounting it.
84 involve special block devices or loopbacks; you merely create a directory on
85 disk with the desired initrd content, cd to that directory, and run (as an
99 First, a directory for the initrd file system has to be created on the
109 procedure should create the /initrd directory.
207 a directory under the current root. Example:
215 [3]). pivot_root moves the current root to a directory under the new
216 root, and puts the new root at its place. The directory for the old root
[all …]
Dsysfs-rules.txt49 - the kernel's path to the device directory without the leading
60 - a directory name, identical to the last element of the devpath
79 - the files in the device directory or files below subdirectories
80 of the same device directory
99 below this directory.
113 "devices" directory at /sys/subsystem/<name>/devices.
136 device directory does not end in /sys/devices/, you can use the
144 directory. These links are also a workaround for the design mistake
146 directory does not contain directories for child devices, these links
DBUG-HUNTING83 Copy the non-working directory next to the working directory
85 One directory at time, try moving the working directory to
93 changes were contained in the sub directory, this should
94 isolate the change to a directory.
102 - You can apply the same technique to each file in the directory,
Defi-stub.txt56 is an EFI-style path and directory elements must be separated with
57 backslashes (\). For example, given the following directory layout,
69 directory is fs0:\Kernels, the following command must be used,
Disapnp.txt12 This directory allows access to ISA PnP cards and logical devices.
Djava.txt18 nonstandard classes (not included in the same directory
26 Read the file 'binfmt_misc.txt' in this directory to know
87 # See if this directory works straight off
95 # Try dereferencing the directory name
108 "directory tree called $FQCLASSP"
367 extension. The directory containing the original .class file will be
Dedac.txt138 EDAC lives in the /sys/devices/system/edac directory.
140 Within this directory there currently reside 2 'edac' components:
196 The representation of the above is reflected in the directory tree
197 in EDAC's sysfs interface. Starting in directory
199 by its own 'mcX' directory, where 'X' is the index of the MC.
209 Under each 'mcX' directory each 'csrowX' is again represented by a
546 There is a three level tree beneath the above 'edac' directory. For example,
552 in this directory are various controls, a symlink and one or more 'instance'
582 In this directory there are two default counter attributes, which are totals of
590 At the lowest directory level is the 'block' directory. There can be 0, 1
[all …]
/linux-4.1.27/Documentation/driver-model/
Dbinding.txt62 A symlink is created in the bus's 'devices' directory that points to
63 the device's directory in the physical hierarchy.
65 A symlink is created in the driver's 'devices' directory that points
66 to the device's directory in the physical hierarchy.
68 A directory for the device is created in the class's directory. A
69 symlink is created in that directory that points to the device's
73 physical directory to either its class directory, or the class's
74 top-level directory. One can also be created to point to its driver's
75 directory also.
Dclass.txt79 sysfs directory structure
81 There is a top-level sysfs directory named 'class'.
83 Each class gets a directory in the class directory, along with two
92 Drivers registered with the class get a symlink in the drivers/ directory
93 that points to the driver's directory (under its bus directory):
102 Each device gets a symlink in the devices/ directory that points to the
103 device's directory in the physical hierarchy:
131 sysfs directory using:
137 class's directory in sysfs.
Dbus.txt87 There is a top-level directory named 'bus'.
89 Each bus gets a directory in the bus directory, along with two default
96 Drivers registered with the bus get a directory in the bus's drivers
97 directory:
108 the bus's devices directory to the device's directory in the physical
138 sysfs directory using:
Ddriver.txt131 When a driver is registered, a sysfs directory is created in its
132 bus's directory. In this directory, the driver can export an interface
136 A future feature of this directory will be a 'devices' directory. This
137 directory will contain symlinks to the directories of devices it
211 driver's directory using:
Doverview.txt104 Whenever a device is inserted into the tree, a directory is created for it.
105 This directory may be populated at each layer of discovery - the global layer,
117 A device-specific driver may also export files in its directory to expose
120 More information about the sysfs directory layout can be found in
121 the other documents in this directory and in the file
Dporting.txt142 Also, the location of the device's sysfs directory depends on a
143 device's parent. sysfs exports a directory structure that mirrors
183 When the device is registered, a directory in sysfs is created.
206 Also, symlinks are created in the bus's 'devices' directory
207 that point to the device's directory in the physical hierarchy.
268 Drivers are exported via sysfs in their bus's 'driver's directory.
355 symlink is created in the driver's sysfs directory that points to the
356 device's physical directory:
/linux-4.1.27/drivers/staging/unisys/Documentation/
Dproc-entries.txt10 /proc/visorchipset/controlvm: This directory contains debugging
25 /proc/uislib/vbus: this is a directory containing entries for each
26 virtual bus. Each numbered sub-directory contains an info entry, which
47 /proc/virtnic/ethX: This is a directory containing entries for each
62 pattern. Each module has its own proc directory with the same name,
63 e.g. visordiag presents a /proc/visordiag directory. Inside of the
64 module's directory are a device directory, which contains one numbered
65 directory for each device provided by that module. Each device has a
67 device. The module directory also has a driver/diag entry, which
91 /proc/visorchipset/partition: This directory contains the guest
/linux-4.1.27/Documentation/usb/
Dgadget-testing.txt33 The function name to use when creating the function directory is "acm".
34 The ACM function provides just one attribute in its function directory:
62 The function name to use when creating the function directory is "ecm".
63 The ECM function provides these attributes in its function directory:
95 The function name to use when creating the function directory is "geth".
96 The ECM subset function provides these attributes in its function directory:
128 The function name to use when creating the function directory is "eem".
129 The EEM function provides these attributes in its function directory:
161 The function name to use when creating the function directory is "ffs".
162 The function directory is intentionally empty and not modifiable.
[all …]
/linux-4.1.27/Documentation/x86/
Dintel_mpx.txt36 2) That setup code allocates (virtual) space for the "bounds directory",
37 points the "bndcfgu" register to the directory (must also set the valid
47 succeed, and notes the location of the bounds directory. Userspace is
48 expected to keep the bounds directory at that locationWe note it
50 to access the bounds directory register is an expensive operation.
52 issues a bndstx instruction. Since the bounds directory is empty at
55 in the bounds directory point to the new table.
62 the table and remove the entry in the directory.
71 * allocates virtual space for the bounds directory (malloc() essentially)
72 * points the hardware BNDCFGU register at the directory
[all …]
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-kernel-livepatch8 The /sys/kernel/livepatch directory contains subdirectories for
16 The patch directory contains subdirectories for each kernel
33 The object directory contains subdirectories for each function
41 The function directory contains attributes regarding the
Dsysfs-kernel-iommu_groups7 name of the sub-directory matches the iommu_group_id()
9 subdirectory is another directory named "devices" with
11 The group directory also optionally contains a "name"
Dsysfs-ibft4 Description: The /sys/firmware/ibft/initiator directory will contain
11 Description: The /sys/firmware/ibft/targetX directory will contain
21 Description: The /sys/firmware/ibft/ethernetX directory will contain
Dsysfs-firmware-ofw7 directory.
25 directory name is the resolved path component name (node
27 in the directory. The contents of each file is the exact
Dsysfs-devices-soc5 The /sys/devices/ directory contains a sub-directory for each
10 The directory created for each SoC will also house information
54 The /sys/bus/soc/ directory contains the usual sub-folders
Dsysfs-class5 The /sys/class directory will consist of a group of
11 All programs that use this directory tree must be able
Dsysfs-firmware-sgi_uv5 The /sys/firmware/sgi_uv directory contains information
8 Under that directory are a number of files:
Dsysfs-class-pwm6 The pwm/ class sub-directory belongs to the Generic PWM
15 A /sys/class/pwm/pwmchipN directory is created for each
46 A /sys/class/pwm/pwmchipN/pwmX directory is created for
Dsysfs-class-mei6 The mei/ class sub-directory belongs to mei device class
14 The /sys/class/mei/meiN directory is created for
Dsysfs-pps5 The /sys/class/pps/ directory will contain files and
13 The /sys/class/pps/ppsX/ directory is related to X-th
14 PPS source into the system. Each directory will
Dsysfs-kernel-boot_params4 Description: The /sys/kernel/boot_params directory contains two
26 The whole boot_params directory structure is like below:
Dsysfs-ata12 For each port, a directory ataX is created where X is the ata_port_id of
29 If a link is behind a port, the directory name is linkX, where X is
50 The name of the directory is devX[.Y].Z where:
Dsysfs-c2port5 The /sys/class/c2port/ directory will contain files and
13 The /sys/class/c2port/c2portX/ directory is related to X-th
14 C2 port into the system. Each directory will contain files to
Dsysfs-devices-memory39 memory section directory name.
77 points to the corresponding NUMA node directory.
91 memory section directory. For example, the following symbolic
Dconfigfs-usb-gadget-ffs4 Description: The purpose of this directory is to create and remove it.
Dsysfs-fs-f2fs70 Controls the directory level for large directory.
Dsysfs-ptp5 This directory contains files and directories
13 This directory contains the attributes of the Nth PTP
68 This directory contains one file for each programmable
Dsysfs-firmware-dmi70 as found in the directory name. It indicates
74 in the parent directory name.
89 is exported in the directory:
Dsysfs-devices-power_resources_D05 The /sys/devices/.../power_resources_D0/ directory is only
Dsysfs-devices-power_resources_wakeup5 The /sys/devices/.../power_resources_wakeup/ directory is only
Dsysfs-devices-power_resources_D3hot5 The /sys/devices/.../power_resources_D3hot/ directory is only
Dsysfs-devices-firmware_node5 The /sys/devices/.../firmware_node directory contains attributes
Dsysfs-devices-power_resources_D15 The /sys/devices/.../power_resources_D1/ directory is only
Dsysfs-devices-power_resources_D25 The /sys/devices/.../power_resources_D2/ directory is only
/linux-4.1.27/Documentation/arm/Marvell/
DREADME26 Linux kernel mach directory: arch/arm/mach-orion5x
27 Linux kernel plat directory: arch/arm/plat-orion
56 Linux kernel mach directory: arch/arm/mach-mvebu
57 Linux kernel plat directory: none
76 Linux kernel mach directory: arch/arm/mach-mv78xx0
77 Linux kernel plat directory: arch/arm/plat-orion
118 Linux kernel mach directory: arch/arm/mach-mvebu
119 Linux kernel plat directory: none
135 Linux kernel mach directory: no code in mainline yet, planned for the future
136 Linux kernel plat directory: no code in mainline yet, planned for the future
[all …]
/linux-4.1.27/Documentation/kbuild/
Dkbuild.txt65 Set the directory to look for the kernel source when building external
67 The directory can be specified in several ways:
76 Specify the output directory when building the kernel.
77 The output directory can also be specified using "O=...".
92 directory name found in the arch/ directory.
125 $4 - default install path (use root directory if blank)
144 INSTALL_MOD_PATH specifies a prefix to MODLIB for module directory
172 $(objtree) is the directory where output files are saved.
173 The output directory is often set using "O=..." on the commandline.
Dmodules.txt88 ($KDIR refers to the path of the kernel source directory.)
93 The directory where the kernel source is located.
94 "make" will actually change to the specified directory
100 directory where the external module (kbuild file) is
111 directory, so a target does not need to be specified. All
112 output files will also be generated in this directory. No
128 Remove all generated files in the module directory only.
307 module, then the file is placed in the same directory as the
314 subsystems have their own directory under include/, such as
331 include/ directory where their source is located, although this
[all …]
Dheaders_install.txt23 The "make headers_install" command can be run in the top level directory of the
30 current architecture. The linux/asm directory of the exported kernel headers
42 directory.) You also can use HDR_ARCH_LIST to specify list of architectures.
43 Remember to provide the appropriate linux/asm directory via "mv" or "ln -s"
Dmakefiles.txt135 This tells kbuild that there is one object in that directory, named
234 combined in a built-in.o for that specific directory.
238 library for that directory.
245 and to be part of a library. Therefore the same directory
253 actually recognize that there is a lib.a being built, the directory
262 directory. Files in subdirectories should be taken care of by
268 ext2 lives in a separate directory, and the Makefile present in fs/
277 down in the ext2 directory.
279 the directory, it is the Makefile in the subdirectory that
282 It is good practice to use a CONFIG_ variable when assigning directory
[all …]
/linux-4.1.27/arch/um/os-Linux/
Dumid.c80 DIR *directory; in remove_files_and_dir() local
86 directory = opendir(dir); in remove_files_and_dir()
87 if (directory == NULL) { in remove_files_and_dir()
94 while ((ent = readdir(directory)) != NULL) { in remove_files_and_dir()
117 closedir(directory); in remove_files_and_dir()
/linux-4.1.27/Documentation/sh/
Dnew-machine.txt15 The first thing to note is the new directory structure. Under 2.4, most
19 companion chip type, and CPU type. Looking at a tree view of this directory
92 In the first case, this is just a matter of making a directory for your
95 it makes more sense to have a common top-level arch/sh/boards/ directory
99 After you have setup your new arch/sh/boards/ directory, remember that you
100 should also add a directory in include/asm-sh for headers localized to this
102 seamlessly with the build system, it's best to have this directory the same
103 as the arch/sh/boards/ directory name, though if your board is again part of
105 overloading), and you can feel free to name the directory after the family
222 the board directory as it appears in arch/sh/boards, even if it is in a
[all …]
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars5 This directory exposes interfaces for interactive with
16 creates a separate directory for each one found. Each
17 directory has a name of the form "<key>-<vendor guid>"
65 in the top-level directory and are used for adding and
Dsysfs-firmware-opal-dump5 This directory exposes interfaces for interacting with
14 0xXX-0xYYYY: A directory for dump of type 0xXX and
16 directory should not be relied upon to
Dsysfs-bus-firewire34 u24 of the respective unit directory entries.
66 Offset of the unit directory within the parent device's
81 These attributes are only created if the root directory of an
82 IEEE 1394 node or the unit directory of an IEEE 1394 unit
103 Mandatory in the root directory according to IEEE 1212.
Dsysfs-firmware-opal-elog5 This directory exposes error log entries retrieved
11 Each log entry has a directory in /sys/firmware/opal/elog.
38 For each log entry (directory), there are the following
/linux-4.1.27/Documentation/dvb/
Dudev.txt33 directory for rule files. The main udev configuration file /etc/udev/udev.conf
34 will tell you the directory where the rules are, most likely it's /etc/udev/rules.d/
36 Create a new rule file in that directory called "dvb.rule" and add the following line:
46 create the proper device node in your /dev/ directory.
Dttusb-dec.txt36 Copy the three files downloaded above into the build-2.4 directory.
45 /lib/firmware directory (depending on configuration of firmware hotplug).
Dopera-firmware.txt7 from the windriver disk into this directory.
/linux-4.1.27/drivers/mtd/
Dredboot.c50 static int directory = CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK; variable
51 module_param(directory, int, 0);
79 if ( directory < 0 ) { in parse_redboot_partitions()
80 offset = master->size + directory * master->erasesize; in parse_redboot_partitions()
90 offset = directory * master->erasesize; in parse_redboot_partitions()
/linux-4.1.27/Documentation/devicetree/bindings/net/
Daltera_tse.txt24 - phy-mode: See ethernet.txt in the same directory.
25 - phy-handle: See ethernet.txt in the same directory.
26 - phy-addr: See ethernet.txt in the same directory. A configuration should
50 - local-mac-address: See ethernet.txt in the same directory.
51 - max-frame-size: See ethernet.txt in the same directory.
Dmarvell-armada-370-neta.txt7 - phy: See ethernet.txt file in the same directory.
8 - phy-mode: See ethernet.txt file in the same directory
Dfsl-fec.txt7 - phy-mode : See ethernet.txt file in the same directory
17 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
30 according to phy.txt in the same directory
Dstmmac.txt13 - phy-mode: See ethernet.txt file in the same directory.
37 - max-frame-size: See ethernet.txt file in the same directory
48 - tx-fifo-depth: See ethernet.txt file in the same directory
49 - rx-fifo-depth: See ethernet.txt file in the same directory
Darc_emac.txt7 - max-speed: see ethernet.txt file in the same directory.
8 - phy: see ethernet.txt file in the same directory.
Dmarvell-pxa168.txt13 - phy-handle: see ethernet.txt file in the same directory.
14 - local-mac-address: see ethernet.txt file in the same directory.
Demac_rockchip.txt10 - phy: see ethernet.txt file in the same directory.
11 - phy-mode: see ethernet.txt file in the same directory.
Damd-xgbe.txt22 - phy-handle: See ethernet.txt file in the same directory
23 - phy-mode: See ethernet.txt file in the same directory
Dsh_eth.txt18 - phy-mode: see ethernet.txt file in the same directory.
19 - phy-handle: see ethernet.txt file in the same directory.
Dallwinner,sun4i-emac.txt8 - phy: see ethernet.txt file in the same directory.
Dcpsw.txt33 - phy-mode : See ethernet.txt file in the same directory
37 - mac-address : See ethernet.txt file in the same directory
Dlpc-eth.txt9 - phy-mode: See ethernet.txt file in the same directory. If the property is
Dcdns-emac.txt10 - phy-mode: see ethernet.txt file in the same directory.
Dsmsc-lan91c111.txt9 - phy-device : see ethernet.txt file in the same directory
Dmarvell-orion-net.txt39 - local-mac-address: See ethernet.txt file in the same directory.
51 - phy-handle: See ethernet.txt file in the same directory.
Dfsl-tsec-phy.txt53 - phy-handle : See ethernet.txt file in the same directory.
54 - fixed-link : See fixed-link.txt in the same directory.
55 - phy-connection-type : See ethernet.txt file in the same directory.
/linux-4.1.27/Documentation/mn10300/
Dcompartmentalisation.txt30 segregated into separate directories under the arch directory:
51 directory for this arch:
59 The appropriate arch/mn10300/unit-ZZZZ directory will also be entered by the
/linux-4.1.27/drivers/nubus/
Dnubus.c209 dir->ptr = dir->base = board->directory; in nubus_get_root_dir()
220 dir->ptr = dir->base = dev->directory; in nubus_get_func_dir()
232 dir->ptr = dir->base = board->directory; in nubus_get_board_dir()
484 dev->directory = dir.base; in nubus_get_functional_resource()
735 board->directory = board->fblock; in nubus_find_rom_dir()
736 nubus_move(&board->directory, in nubus_find_rom_dir()
788 board->directory = dir.base; in nubus_find_rom_dir()
793 board->directory = board->fblock; in nubus_find_rom_dir()
794 nubus_move(&board->directory, nubus_expand32(board->doffset), board->lanes); in nubus_find_rom_dir()
/linux-4.1.27/include/linux/
Dnubus.h31 unsigned char* directory; member
71 unsigned char* directory; member
/linux-4.1.27/drivers/firewire/
Dcore-device.c63 static const u32 *search_leaf(const u32 *directory, int search_key) in search_leaf() argument
68 fw_csr_iterator_init(&ci, directory); in search_leaf()
123 int fw_csr_string(const u32 *directory, int key, char *buf, size_t size) in fw_csr_string() argument
125 const u32 *leaf = search_leaf(directory, key); in fw_csr_string()
133 static void get_ids(const u32 *directory, int *id) in get_ids() argument
138 fw_csr_iterator_init(&ci, directory); in get_ids()
152 get_ids(unit->directory, id); in get_modalias_ids()
273 dir = fw_unit(dev)->directory; in show_immediate()
306 dir = fw_unit(dev)->directory; in show_text_leaf()
389 (int)(unit->directory - device->config_rom)); in rom_index_show()
[all …]
/linux-4.1.27/Documentation/early-userspace/
DREADME33 CONFIG_INITRAMFS_SOURCE and directory and file names are not allowed in
47 A source directory will have it and all of its contents packaged. The
48 specified directory name will be mapped to '/'. When packaging a
49 directory, limited user and group ID translation can be performed.
61 can create a 'root-image' directory and install all files into it.
71 gen_initramfs_list.sh. If a directory is specified as an argument then
73 usr/gen_init_cpio file directives are output. If a directory is
76 directives from directory scanning and file contents copying are
/linux-4.1.27/scripts/
Dpatch-kernel71 source directory defaults to /usr/src/linux,
72 patch directory defaults to the current directory,
Dgen_initramfs_list.sh23 directory. "squash" forces all files to uid 0.
26 directory. "squash" forces all files to gid 0.
27 <cpio_source> File list or directory for cpio archive.
Dmkmakefile43 MAKEFLAGS += --no-print-directory
/linux-4.1.27/Documentation/netlabel/
Dintroduction.txt25 directory, consult '00-INDEX' for filenames.
33 names can be found in the 'net/netlabel/' directory as comments in the
46 found in this directory.
/linux-4.1.27/Documentation/arm/
DCCN.txt16 The "format" directory describes format of the config, config1
18 directory provides configuration templates for all documented
30 directory, with first 8 configurable by user and additional
/linux-4.1.27/Documentation/ABI/
DREADME1 This directory attempts to document the ABI between the Linux kernel and
13 This directory documents the interfaces that the developer has
21 This directory documents interfaces that are felt to be stable,
35 This directory documents interfaces that are still remaining in
41 This directory contains a list of the old interfaces that have
/linux-4.1.27/Documentation/acpi/
Dnamespace.txt236 directory in sysfs will contain the 'path' attribute whose value is
241 column), so its sysfs directory will not contain the 'path'
247 its namespace path will be present in its sysfs directory. For
262 the corresponding ACPI namespace node. The object's sysfs directory
291 directory contains the "physical_node" symbolic link to the sysfs
292 directory of the target device object. In turn, the target device's
293 sysfs directory will then contain the "firmware_node" symbolic link to
294 the sysfs directory of the companion ACPI device object.
299 bus number of the parent PCI bridge is 0, the sysfs directory
302 /sys/devices/pci0000:00/0000:00:02:0/ sysfs directory of the
[all …]
/linux-4.1.27/tools/usb/usbip/
DINSTALL20 those values to create a `Makefile' in each directory of the package.
47 1. `cd' to the directory containing the package's source code and type
62 source code directory by typing `make clean'. To also remove the
93 own directory. To do this, you can use GNU `make'. `cd' to the
94 directory where you want the object files and executables to go and run
96 source code in the directory that `configure' is in and in `..'.
99 architecture at a time in the source code directory. After you have
117 In addition, if you use an unusual directory layout you can give
232 Look for the package's source code in directory DIR. Usually
233 `configure' can determine that directory automatically.
/linux-4.1.27/Documentation/cma/
Ddebugfs.txt4 Each CMA zone represents a directory under <debugfs>/cma/, indexed by the
9 The structure of the files created under that directory is as follows:
/linux-4.1.27/fs/cramfs/
DREADME6 swapped around (though it does care that directory entries (inodes) in
7 a given directory are contiguous, as this is used by readdir).
27 a directory's entries before recursing down its subdirectories: the
28 same order as `ls -AUR' (but without the /^\..*:$/ directory header
32 Beginning in 2.4.7, directory entries are sorted. This optimization
34 exist, speeds up user-space directory sorts, etc.
52 The order of <file_data>'s is a depth-first descent of the directory
/linux-4.1.27/Documentation/devicetree/bindings/pwm/
Drenesas,tpu-pwm.txt15 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
19 Please refer to pwm.txt in this directory for details of the common PWM bindings
Dti,twl-pwm.txt9 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
Dspear-pwm.txt8 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
Datmel-tcb-pwm.txt5 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
Dmxs-pwm.txt6 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
Dti,twl-pwmled.txt9 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
Datmel-pwm.txt8 - #pwm-cells: Should be 3. See pwm.txt in this directory for a
Dpwm-sun4i.txt8 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
Dvt8500-pwm.txt6 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
Dbrcm,kona-pwm.txt9 - #pwm-cells: Should be 3. See pwm.txt in this directory for a
Dpwm-rockchip.txt10 - #pwm-cells: must be 2 (rk2928) or 3 (rk3288). See pwm.txt in this directory
Dpwm-bcm2835.txt9 - #pwm-cells: Should be 2. See pwm.txt in this directory for a description of
Dnxp,pca9685-pwm.txt6 - #pwm-cells: Should be 2. See pwm.txt in this directory for a description of
/linux-4.1.27/tools/scripts/
DMakefile.include16 $(if $(OUTDIR),, $(error output directory "$(OUTPUT)" does not exist))
44 PRINT_DIR = --no-print-directory
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-mux-pca954x.txt13 - Standard I2C mux properties. See i2c-mux.txt in this directory.
14 - I2C child bus nodes. See i2c-mux.txt in this directory.
Di2c-mux-gpio.txt25 * Standard I2C mux properties. See mux.txt in this directory.
26 * I2C child bus nodes. See mux.txt in this directory.
Di2c-mux-pinctrl.txt31 * Standard I2C mux properties. See mux.txt in this directory.
33 * I2C child bus nodes. See mux.txt in this directory.
/linux-4.1.27/tools/testing/selftests/ftrace/
DREADME19 Or you can also run testcases under given directory:
29 * The working directory of the script is <debugfs>/tracing/.
36 * You can add a directory for your testcases under test.d/ if needed.
/linux-4.1.27/Documentation/networking/
Dfore200e.txt24 in the linux/drivers/atm directory for details and restrictions.
52 to some directory, such as linux/drivers/atm.
55 Expected pathnames are absolute or relative to the drivers/atm directory.
Ddl2k.txt70 Kernels 2.4.7. Copy the files to a directory and enter the following command
156 1. Copy dl2k.o to the network modules directory, typically
159 /etc/modprobe.d/ directory. Add the following lines:
168 /etc/sysconfig/network-scripts directory, and create a configuration
276 /usr/src/linux/include, which is the default include directory configured
/linux-4.1.27/
D.gitignore53 # Debian directory (make deb-pkg)
58 # tar directory (make tar*-pkg)
/linux-4.1.27/Documentation/filesystems/caching/
Dcachefiles.txt34 CacheFiles is a caching backend that's meant to use as a cache a directory on
104 Specify the directory containing the root of the cache. Mandatory.
233 The CacheFiles module will create two directories in the directory it was
240 The active cache objects all reside in the first directory. The CacheFiles
244 The daemon uses dnotify to monitor the graveyard directory, and will delete
249 "J...". Note that the "cache/" directory is itself a special index.
253 directory, data objects will have a file in the directory called "data" that
260 If an object has children, then it will be represented as a directory.
261 Immediately in the representative directory are a collection of directories
263 this directory, if possible, will be placed the representations of the child
[all …]
/linux-4.1.27/Documentation/virtual/kvm/devices/
DREADME1 This directory contains specific device bindings for KVM_CAP_DEVICE_CTRL.
/linux-4.1.27/tools/testing/ktest/examples/
DREADME1 This directory contains example configs to use ktest for various tasks.
25 include/ - The include directory holds default configs that can be
/linux-4.1.27/Documentation/s390/
Dzfcpdump.txt37 * kernel: <zfcpdump directory>/zfcpdump.image
38 * ramdisk: <zfcpdump directory>/zfcpdump.rd
40 The zfcpdump directory is defined in the s390-tools package.
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DOverview.txt20 included under the arch/arm/mach-s3c2416 directory. Note, whilst core
41 This directory should be kept to items shared between the platform
44 Each cpu has a directory with the support files for it, and the
49 arch/arm/mach-s3c2410 directory./include/mach
61 this directory, the name becomes invalid. We stick to s3c2440-<x>
140 Documentation/arm directory before submitting patches. The
216 documentation in GPIO.txt in the same directory as this file.
DS3C2412.txt42 s3c2410 driver in the drivers/serial directory.
49 s3c2410 driver in the drivers/mtd/nand directory.
/linux-4.1.27/firmware/
DREADME.AddingFirmware5 This directory is only here to contain firmware images extracted from old
12 This directory is _NOT_ for adding arbitrary new firmware images. The
/linux-4.1.27/scripts/kconfig/
DMakefile63 --directory=$(srctree) --directory=$(objtree) \
246 $(HOSTCXX) -print-multi-os-directory > /dev/null 2>&1 && \
247 osdir=x$$($(HOSTCXX) -print-multi-os-directory); \
/linux-4.1.27/Documentation/filesystems/nfs/
Dpnfs.txt66 Files-layout-driver code is in: fs/nfs/filelayout/.. directory
67 Objects-layout-deriver code is in: fs/nfs/objlayout/.. directory
68 Blocks-layout-deriver code is in: fs/nfs/blocklayout/.. directory
69 Flexfiles-layout-driver code is in: fs/nfs/flexfilelayout/.. directory
DExporting47 2/ The dcache must be prepared for a newly found (via ->lookup) directory
68 loose directory dentries at lookup time. They are:
73 In the case of a directory, care is taken that only one dentry
126 When given a dentry for a directory, this should return a dentry for
135 in the directory identified by the parent dentry, which leads to the
/linux-4.1.27/Documentation/RCU/
Drcu.txt50 See the UP.txt file in this directory.
64 See the checklist.txt file in this directory.
91 See the RTFP.txt file in this directory.
94 o What are all these files in this directory?
/linux-4.1.27/Documentation/devicetree/bindings/panel/
Dlg,lp129qe.txt7 in simple-panel.txt in this directory.
Dinnolux,n156bge-l21.txt7 in simple-panel.txt in this directory.
Dsamsung,ltn101nt05.txt7 in simple-panel.txt in this directory.
Dpanasonic,vvx10f004b00.txt7 in simple-panel.txt in this directory.
Dortustech,com43h4m85ulc.txt7 in simple-panel.txt in this directory.
Dinnolux,at043tn24.txt7 in simple-panel.txt in this directory.
Dauo,b101aw03.txt7 in simple-panel.txt in this directory.
Dsamsung,ltn140at29-301.txt7 in simple-panel.txt in this directory.
Dauo,b101ean01.txt7 in simple-panel.txt in this directory.
Dauo,b101xtn01.txt7 in simple-panel.txt in this directory.
Dinnolux,n116bge.txt7 in simple-panel.txt in this directory.
Dfoxlink,fl500wvr00-a0t.txt7 in simple-panel.txt in this directory.
Dlg,ld070wx3-sl01.txt7 in simple-panel.txt in this directory.
Dlg,lh500wx1-sd03.txt7 in simple-panel.txt in this directory.
Dgiantplus,gpg482739qs5.txt7 in simple-panel.txt in this directory.
Dinnolux,zj070na-01p.txt7 in simple-panel.txt in this directory.
Dchunghwa,claa101wb03.txt7 in simple-panel.txt in this directory.
Dchunghwa,claa101wa01a.txt7 in simple-panel.txt in this directory.
Dedt,et057090dhu.txt7 in simple-panel.txt in this directory.
Dhannstar,hsd070pww1.txt7 in simple-panel.txt in this directory.
Dauo,b133xtn01.txt7 in simple-panel.txt in this directory.
Dhit,tx23d38vm0caa.txt7 in simple-panel.txt in this directory.
Dampire,am800480r3tmqwa1h.txt7 in simple-panel.txt in this directory.
Dinnolux,g121i1-l01.txt7 in simple-panel.txt in this directory.
Davic,tm070ddh03.txt7 in simple-panel.txt in this directory.
Dauo,b116xw03.txt7 in simple-panel.txt in this directory.
Dauo,b133htn01.txt7 in simple-panel.txt in this directory.
Dshelly,sca07010-bfn-lnn.txt7 in simple-panel.txt in this directory.
Dedt,et070080dh6.txt10 in simple-panel.txt in this directory.
Dedt,etm0700g0dh6.txt10 in simple-panel.txt in this directory.
/linux-4.1.27/fs/udf/
DMakefile9 directory.o misc.o udftime.o unicode.o
/linux-4.1.27/Documentation/filesystems/pohmelfs/
Dnetwork_protocol.txt28 NETFS_READDIR = 1, /* Read directory for given inode number */
31 NETFS_CREATE, /* Create directory entry */
32 NETFS_REMOVE, /* Remove directory entry */
66 @id - local inode number of the directory to read.
107 @id - local inode number of the directory to look object in.
/linux-4.1.27/fs/exofs/
DBUGS1 - Out-of-space may cause a severe problem if the object (and directory entry)
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dkvm-recheck-lock.sh30 echo Unreadable results directory: $i
Dkvm.sh262 echo Results directory: $resdir/$ds
386 echo Results directory: $resdir/$ds
Dconfiginit.sh54 echo Bad build directory: \"$builddir\"
Dkvm-recheck-rcu.sh30 echo Unreadable results directory: $i
/linux-4.1.27/fs/notify/dnotify/
DKconfig6 Dnotify is a directory-based per-fd file change notification system
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dfsl,imx25-pinctrl.txt3 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
/linux-4.1.27/Documentation/filesystems/configfs/
Dconfigfs.txt117 appears as a directory at the top of the configfs filesystem. A
199 configfs directory, it must define a configfs_attribute describing it.
248 …ethod. If provided, this method is called from mkdir(2) in the group's directory. The subsystem …
286 directory is not empty.
464 committed via rename(2). The item is moved from a directory where it
465 can be modified to a directory where it cannot.
470 subdirectories: "live" and "pending". The "live" directory does not
472 "pending" directory does allow mkdir(2) and rmdir(2). An item is
473 created in the "pending" directory. Its attributes can be modified at
475 directory. At this point, the subsystem receives the ->commit_item()
[all …]
/linux-4.1.27/drivers/scsi/aic7xxx/aicasm/
Daicasm.h60 char *directory; member
/linux-4.1.27/Documentation/arm/Samsung/
DOverview.txt42 The directory layout is currently being restructured, and consists of
54 S5P specific systems. Not all S5Ps use all the features in this directory
/linux-4.1.27/tools/perf/Documentation/
Dperf-annotate.txt84 --symfs=<directory>::
85 Look for files with symbols relative to this directory.
Dperf-test.txt16 also will look for a directory with more tests in the form of scripts.
Dperf-data.txt28 Triggers the CTF conversion, specify the path of CTF data directory.
/linux-4.1.27/tools/perf/
DMakefile81 @$(MAKE) -f tests/make --no-print-directory
/linux-4.1.27/Documentation/devicetree/bindings/reset/
Dallwinner,sunxi-clock-reset.txt4 Please also refer to reset.txt in this directory for common reset
/linux-4.1.27/fs/hpfs/
Ddir.c245 if (de->directory) in hpfs_lookup()
259 if (!de->directory) hpfs_result->i_parent_dir = dir->i_ino; in hpfs_lookup()
282 if (!de->directory) { in hpfs_lookup()
/linux-4.1.27/sound/firewire/bebob/
Dbebob.c84 err = fw_csr_string(bebob->unit->directory, CSR_MODEL, in name_device()
149 if (fw_csr_string(unit->directory, CSR_MODEL, name, sizeof(name)) < 0) in get_saffire_spec()
163 if (fw_csr_string(unit->directory, CSR_MODEL, name, sizeof(name)) < 0) in check_audiophile_booted()
/linux-4.1.27/drivers/base/
DKconfig37 It provides a fully functional /dev directory, where usually
59 rescue mode with init=/bin/sh, even when the /dev directory
126 the directory specified by the EXTRA_FIRMWARE_DIR option, which is
130 the usb8388.bin file into the firmware directory, and build the kernel.
141 string "Firmware blobs root directory"
145 This option controls the directory in which the kernel build system
149 some other directory containing the firmware files.
/linux-4.1.27/fs/dlm/
DKconfig15 appear as a file in the "dlm" directory. The output is the
/linux-4.1.27/drivers/lguest/
DKconfig8 "lguest" command found in the tools/lguest directory.
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-lp3943.txt6 - #gpio-cells: Should be 2. See gpio.txt in this directory for a
/linux-4.1.27/drivers/net/ethernet/qlogic/qlcnic/
Dqlcnic_init.c755 struct uni_table_desc *directory = (struct uni_table_desc *) &unirom[0]; in qlcnic_get_table_desc() local
756 entries = le32_to_cpu(directory->num_entries); in qlcnic_get_table_desc()
760 u32 offs = le32_to_cpu(directory->findex) + in qlcnic_get_table_desc()
761 i * le32_to_cpu(directory->entry_size); in qlcnic_get_table_desc()
777 struct uni_table_desc *directory = (struct uni_table_desc *) &unirom[0]; in qlcnic_validate_header() local
785 entries = le32_to_cpu(directory->num_entries); in qlcnic_validate_header()
786 entry_size = le32_to_cpu(directory->entry_size); in qlcnic_validate_header()
787 tab_size = le32_to_cpu(directory->findex) + (entries * entry_size); in qlcnic_validate_header()
/linux-4.1.27/tools/lib/api/
DMakefile14 MAKEFLAGS += --no-print-directory
/linux-4.1.27/Documentation/security/
DSmack.txt59 The /sys/fs/smackfs directory is created by the kernel.
82 on a directory when an object is created in the directory and
84 to the directory includes the transmute ("t") mode the object
85 gets the label of the directory instead of the label of the
86 creating process. If the object being created is a directory
448 search a directory requires execute access. Creating a file with write access
449 requires both read and write access on the containing directory. Deleting a
451 directory. It is possible that a user may be able to see that a file exists
453 containing directory but not to the differently labeled file. This is an
454 artifact of the file name being data in the directory, not a part of the file.
[all …]
/linux-4.1.27/Documentation/sysctl/
DREADME43 at run-time, and the /proc/sys/ directory is there so that you
52 As a quick 'ls /proc/sys' will show, the directory consists of

1234