Home
last modified time | relevance | path

Searched full:follow (Results 1 – 25 of 1067) sorted by relevance

12345678910>>...43

/Linux-v5.4/drivers/scsi/mvsas/
Dmv_64xx.h53 /* ports 1-3 follow after this */
56 /* ports 5-7 follow after this */
60 /* ports 1-3 follow after this */
62 /* ports 5-7 follow after this */
68 /* ports 1-3 follow after this */
71 /* ports 5-7 follow after this */
75 /* ports 1-3 follow after this */
78 /* ports 5-7 follow after this */
Dmv_94xx.h72 /* ports 1-3 follow after this */
75 /* ports 5-7 follow after this */
79 /* ports 1-3 follow after this */
81 /* ports 5-7 follow after this */
84 /* ports 1-3 follow after this */
87 /* ports 5-7 follow after this */
91 /* phys 1-3 follow after this */
94 /* phys 1-3 follow after this */
/Linux-v5.4/Documentation/devicetree/bindings/regulator/
Dqcom,spmi-regulator.txt203 BIT(0) = follow HW0_EN signal
204 BIT(1) = follow HW1_EN signal
205 BIT(2) = follow HW2_EN signal
206 BIT(3) = follow HW3_EN signal
215 BIT(0) = follow HW0_EN signal
216 BIT(1) = follow HW1_EN signal
217 BIT(2) = follow HW2_EN signal
218 BIT(3) = follow HW3_EN signal
219 BIT(4) = follow PMIC awake state
/Linux-v5.4/drivers/acpi/acpica/
Damlresrc.h261 /* res_source_index, res_source optional fields follow */
288 * Optional fields follow immediately:
330 * Optional fields follow immediately:
348 * Optional fields follow immediately:
366 * Optional fields follow immediately:
387 * Optional fields follow immediately:
407 * Optional fields follow immediately:
424 * Optional fields follow immediately:
443 * Optional fields follow immediately:
463 * Optional fields follow immediately:
/Linux-v5.4/Documentation/devicetree/bindings/power/reset/
Dqcom,pon.txt17 -pwrkey: Specifies the subnode pwrkey and should follow the
19 -resin: Specifies the subnode resin and should follow the
22 The rest of the properties should follow the generic reboot-mode description
/Linux-v5.4/include/uapi/linux/
Dmount.h67 #define MOVE_MOUNT_F_SYMLINKS 0x00000001 /* Follow symlinks on from path */
68 #define MOVE_MOUNT_F_AUTOMOUNTS 0x00000002 /* Follow automounts on from path */
70 #define MOVE_MOUNT_T_SYMLINKS 0x00000010 /* Follow symlinks on to path */
71 #define MOVE_MOUNT_T_AUTOMOUNTS 0x00000020 /* Follow automounts on to path */
Dfcntl.h82 #define AT_SYMLINK_NOFOLLOW 0x100 /* Do not follow symbolic links. */
85 #define AT_SYMLINK_FOLLOW 0x400 /* Follow symbolic links. */
/Linux-v5.4/tools/include/uapi/linux/
Dmount.h67 #define MOVE_MOUNT_F_SYMLINKS 0x00000001 /* Follow symlinks on from path */
68 #define MOVE_MOUNT_F_AUTOMOUNTS 0x00000002 /* Follow automounts on from path */
70 #define MOVE_MOUNT_T_SYMLINKS 0x00000010 /* Follow symlinks on to path */
71 #define MOVE_MOUNT_T_AUTOMOUNTS 0x00000020 /* Follow automounts on to path */
Dfcntl.h82 #define AT_SYMLINK_NOFOLLOW 0x100 /* Do not follow symbolic links. */
85 #define AT_SYMLINK_FOLLOW 0x400 /* Follow symbolic links. */
/Linux-v5.4/Documentation/admin-guide/
Dreporting-bugs.rst139 Follow up
145 Linux kernel maintainers expect bug reporters to be able to follow up on
149 never follow up on a request to try out a fix.
152 on a supported kernel, even if you can't follow up with retests. Follow
/Linux-v5.4/drivers/media/usb/as102/
Das10x_cmd_cfg.c57 /* parse response: context command do not follow the common response */ in as10x_cmd_get_context()
115 /* parse response: context command do not follow the common response */ in as10x_cmd_set_context()
129 * - AUTO : 0x2 => eLNA follow hysteresis parameters
177 * Since the contex command response does not follow the common
/Linux-v5.4/Documentation/media/uapi/v4l/
Dvidioc-g-dv-timings.rst230 - The timings follow the CEA-861 Digital TV Profile standard
232 - The timings follow the VESA Discrete Monitor Timings standard
234 - The timings follow the VESA Coordinated Video Timings standard
236 - The timings follow the VESA Generalized Timings Formula standard
238 - The timings follow the SDI Timings standard.
/Linux-v5.4/Documentation/networking/
Dnf_flowtable.txt10 Initial packets follow the classic forwarding path, once the flow enters the
28 follow the classic forwarding path unless the user explicitly instruct packets
67 neigh_xmit(). Fragmented traffic is passed up to follow the classic forwarding
/Linux-v5.4/Documentation/firmware-guide/acpi/
DDSD-properties-rules.rst48 Valid property sets must follow the guidance given by the Device Properties UUID
55 return property sets which do not follow that rule from _DSD in data packages
81 It often is useful to make _DSD return property sets that follow Device Tree
/Linux-v5.4/include/video/
Dkyro.h55 * Added the follow IOCTLS for the creation of overlay services...
67 * The follow 3 structures are used to pass data from user space into the kernel
/Linux-v5.4/arch/xtensa/include/asm/
Dtlbflush.h90 * caller must follow up with an 'isync', which can be relatively
95 /* Caller must follow up with 'isync'. */ in invalidate_itlb_entry_no_isync()
101 /* Caller must follow up with 'isync'. */ in invalidate_dtlb_entry_no_isync()
/Linux-v5.4/Documentation/process/
Dcode-of-conduct-interpretation.rst97 or bug tracking tools should follow the guidelines of the Code of
100 performed using a kernel.org email account must follow the Code of
102 corporate email account must follow the specific rules of that
Dstable-kernel-rules.rst29 - It must follow the
38 - If the patch covers files in net/ or drivers/net please follow netdev stable
45 process but should follow the procedures in
/Linux-v5.4/net/dsa/
Dtag_sja1105.c41 * Structure of the meta-data follow-up frame. in sja1105_meta_unpack()
130 * sent as a follow-up to the link-local frame on the CPU port.
136 * meta follow-up. It also ensures strict ordering between ports (lower ports
141 * meta follow-up frame. The full timestamp will be reconstructed later in a
/Linux-v5.4/include/linux/
Dnamei.h20 #define LOOKUP_FOLLOW 0x0001 /* follow links at the end */
24 #define LOOKUP_DOWN 0x8000 /* follow mounts in the starting point */
/Linux-v5.4/Documentation/filesystems/
Doverlayfs.txt182 feature and follow redirects even if turned off.
197 - "redirect_dir=follow":
217 turning off redirect follow (e.g. "redirect_dir=nofollow").
289 Note: redirect_dir={off|nofollow|follow(*)} conflicts with metacopy=on, and
292 (*) redirect_dir=follow only conflicts with metacopy=on if upperdir=... is
472 used NFS export in this setup requires turning off redirect follow (e.g.
Dgfs2-uevents.txt15 is successful, an ONLINE uevent will follow. If it is not successful
16 then a REMOVE uevent will follow.
/Linux-v5.4/drivers/input/misc/
Dideapad_slidebar.c34 * STD 'heartbeat' lights follow the finger
35 * ONMOV no lights lights follow the finger
36 * LAST at last pos lights follow the finger
/Linux-v5.4/Documentation/filesystems/ext4/
Ddirectory.rst287 - Maximum number of dx\_entries that can follow this header, plus 1 for
292 - Actual number of dx\_entries that follow this header, plus 1 for the
356 - Maximum number of dx\_entries that can follow this header, plus 1 for
361 - Actual number of dx\_entries that follow this header, plus 1 for the
/Linux-v5.4/fs/btrfs/
Dprint-tree.h10 void btrfs_print_tree(struct extent_buffer *c, bool follow);

12345678910>>...43