Searched full:symbolic (Results 1 – 25 of 517) sorted by relevance
12345678910>>...21
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | devices.rst | 67 the /dev directory. It is preferred that symbolic links use the same
69 classified as "hard" or "symbolic" depending on the preferred type of
78 /dev/fd /proc/self/fd symbolic File descriptors
79 /dev/stdin fd/0 symbolic stdin file descriptor
80 /dev/stdout fd/1 symbolic stdout file descriptor
81 /dev/stderr fd/2 symbolic stderr file descriptor
82 /dev/nfsd socksys symbolic Required by iBCS-2
83 /dev/X0R null symbolic Required by iBCS-2
95 /dev/core /proc/kcore symbolic Backward compatibility
96 /dev/ramdisk ram0 symbolic Backward compatibility
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | devices.rst | 66 the /dev directory. It is preferred that symbolic links use the same
68 classified as "hard" or "symbolic" depending on the preferred type of
77 /dev/fd /proc/self/fd symbolic File descriptors
78 /dev/stdin fd/0 symbolic stdin file descriptor
79 /dev/stdout fd/1 symbolic stdout file descriptor
80 /dev/stderr fd/2 symbolic stderr file descriptor
81 /dev/nfsd socksys symbolic Required by iBCS-2
82 /dev/X0R null symbolic Required by iBCS-2
94 /dev/core /proc/kcore symbolic Backward compatibility
95 /dev/ramdisk ram0 symbolic Backward compatibility
[all …]
|
| /kernel/linux/linux-5.10/drivers/media/usb/pvrusb2/ |
| D | pvrusb2-ctrl.h | 66 /* Return true if control has custom symbolic representation */
69 /* Convert a given mask/val to a custom symbolic value */
75 /* Convert a symbolic value to a mask/value pair */
80 /* Convert a given mask/val to a symbolic value */
86 /* Convert a symbolic value to a mask/value pair */
91 /* Convert a given mask/val to a symbolic value - must already be
|
| /kernel/linux/linux-6.6/drivers/media/usb/pvrusb2/ |
| D | pvrusb2-ctrl.h | 66 /* Return true if control has custom symbolic representation */
69 /* Convert a given mask/val to a custom symbolic value */
75 /* Convert a symbolic value to a mask/value pair */
80 /* Convert a given mask/val to a symbolic value */
86 /* Convert a symbolic value to a mask/value pair */
91 /* Convert a given mask/val to a symbolic value - must already be
|
| /kernel/linux/linux-5.10/fs/squashfs/ |
| D | symlink.c | 12 * This file implements code to handle symbolic links.
14 * The data contents of symbolic links are stored inside the symbolic
15 * link inode within the inode table. This allows the normally small symbolic
17 * compression than if the symbolic link was compressed individually.
|
| /kernel/linux/linux-6.6/fs/squashfs/ |
| D | symlink.c | 12 * This file implements code to handle symbolic links.
14 * The data contents of symbolic links are stored inside the symbolic
15 * link inode within the inode table. This allows the normally small symbolic
17 * compression than if the symbolic link was compressed individually.
|
| /kernel/linux/linux-6.6/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 84 The <EPF Device> directory can have a list of symbolic links
85 (<Symlink EPF Device 31>) to other <EPF Device>. These symbolic links should
108 The <EPC Device> directory will have a list of symbolic links to
109 <EPF Device>. These symbolic links should be created by the user to
121 | <Symbolic Link: Function>
|
| /kernel/linux/linux-5.10/include/uapi/scsi/fc/ |
| D | fc_ns.h | 32 FC_NS_GSPN_ID = 0x0118, /* get symbolic port name */
41 FC_NS_RSPN_ID = 0x0218, /* reg symbolic port name */
43 FC_NS_RSNN_NN = 0x0239, /* reg symbolic node name */
169 * RSNN_NN request - register symbolic node name
178 * RSPN_ID request - register symbolic port name
|
| /kernel/linux/linux-6.6/include/uapi/scsi/fc/ |
| D | fc_ns.h | 32 FC_NS_GSPN_ID = 0x0118, /* get symbolic port name */
41 FC_NS_RSPN_ID = 0x0218, /* reg symbolic port name */
43 FC_NS_RSNN_NN = 0x0239, /* reg symbolic node name */
169 * RSNN_NN request - register symbolic node name
178 * RSPN_ID request - register symbolic port name
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-memory | 80 When CONFIG_NUMA is enabled, a symbolic link that
83 For example, the following symbolic link is created for
94 /sys/devices/system/node/nodeX/memoryY is a symbolic link that
96 memory section directory. For example, the following symbolic
|
| D | sysfs-bus-pci | 150 This symbolic link appears when hardware supports the SR-IOV
152 The symbolic link points to the PCI device sysfs entry of the
159 This symbolic link appears when hardware supports the SR-IOV
162 The symbolic link points to the PCI device sysfs entry of
169 This symbolic link appears when a device is a Virtual Function.
170 The symbolic link points to the PCI device sysfs entry of the
177 This symbolic link points to the PCI hotplug controller driver
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | affs.rst | 95 symbolic links on an AFFS partition. Default = "/".
99 When symbolic links with an absolute path are created
147 Symbolic links
152 with symbolic links. While Linux has a file system with exactly one
155 these entities are called "volumes". They have symbolic names which
156 can be used to access them. Thus, symbolic links can point to a
165 /amiga/WB and /amiga/Graphics). A symbolic link referring to
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | affs.rst | 95 symbolic links on an AFFS partition. Default = "/".
99 When symbolic links with an absolute path are created
147 Symbolic links
152 with symbolic links. While Linux has a file system with exactly one
155 these entities are called "volumes". They have symbolic names which
156 can be used to access them. Thus, symbolic links can point to a
165 /amiga/WB and /amiga/Graphics). A symbolic link referring to
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-devices-memory | 93 When CONFIG_NUMA is enabled, a symbolic link that
96 For example, the following symbolic link is created for
107 /sys/devices/system/node/nodeX/memoryY is a symbolic link that
109 memory section directory. For example, the following symbolic
|
| /kernel/linux/linux-6.6/fs/ |
| D | fs_types.c | 34 * * DT_LNK - Symbolic link
75 * * FT_SYMLINK - Symbolic link
98 * * DT_LNK - Symbolic link
|
| /kernel/linux/linux-5.10/fs/ |
| D | fs_types.c | 34 * * DT_LNK - Symbolic link
75 * * FT_SYMLINK - Symbolic link
98 * * DT_LNK - Symbolic link
|
| /kernel/linux/linux-6.6/Documentation/i2c/ |
| D | i2c-sysfs.rst | 40 There is a list of symbolic links under that directory. The links that
139 is to read the symbolic link ``device`` under the I2C bus directory by using
142 An alternative symbolic link to check is ``mux_device``. This link only exists
147 If the symbolic link points to a directory ending with ``.i2c``, it should be a
156 In this case, ``i2c-7`` is a physical I2C bus, so it does not have the symbolic
161 On the other hand, if the symbolic link points to another I2C bus, the I2C bus
223 # cd the channel symbolic link
326 There is a symbolic link named ``driver`` to tell what Linux kernel driver was
351 will have symbolic link ``channel-*`` inside its device directory.
352 These symbolic links point to their logical I2C bus directories::
|
| /kernel/linux/linux-5.10/include/drm/ |
| D | drm_property.h | 33 * struct drm_property_enum - symbolic values for enumerations
36 * @name: symbolic name for the enum
38 * For enumeration and bitmask properties this structure stores the symbolic
58 * symbolic property will have the same modeset object ID on all modeset
162 * @name: symbolic name of the properties
187 * List of &drm_prop_enum_list structures with the symbolic names for
|
| /kernel/linux/linux-6.6/include/drm/ |
| D | drm_property.h | 33 * struct drm_property_enum - symbolic values for enumerations
35 * @name: symbolic name for the enum
37 * For enumeration and bitmask properties this structure stores the symbolic
65 * symbolic property will have the same modeset object ID on all modeset
169 * @name: symbolic name of the properties
194 * List of &drm_prop_enum_list structures with the symbolic names for
|
| /kernel/linux/linux-5.10/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 89 The <EPC Device> directory will have a list of symbolic links to
90 <EPF Device>. These symbolic links should be created by the user to
101 | <Symbolic Link: Function>
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/i915/ |
| D | intel_step.h | 69 * Symbolic steppings that do not match the hardware. These are valid both as gt
70 * and display steppings as symbolic names.
|
| /kernel/linux/linux-5.10/fs/xfs/scrub/ |
| D | symlink.c | 18 /* Set us up to scrub a symbolic link. */
32 /* Symbolic links. */
|
| /kernel/linux/linux-6.6/fs/xfs/scrub/ |
| D | symlink.c | 18 /* Set us up to scrub a symbolic link. */
31 /* Symbolic links. */
|
| /kernel/linux/linux-6.6/drivers/scsi/bfa/ |
| D | bfa_defs_fcs.h | 64 * symbolic names for base port/virtual port
88 struct bfa_lport_symname_s sym_name; /* vm port symbolic name */
89 struct bfa_lport_symname_s node_sym_name; /* Node symbolic name */
342 * port/node symbolic names for rport
398 struct bfa_rport_symname_s symname; /* Symbolic Name */
|
| /kernel/linux/linux-5.10/drivers/scsi/bfa/ |
| D | bfa_defs_fcs.h | 64 * symbolic names for base port/virtual port
88 struct bfa_lport_symname_s sym_name; /* vm port symbolic name */
89 struct bfa_lport_symname_s node_sym_name; /* Node symbolic name */
342 * port/node symbolic names for rport
398 struct bfa_rport_symname_s symname; /* Symbolic Name */
|
12345678910>>...21