Home
last modified time | relevance | path

Searched refs:follow (Results 1 – 25 of 217) sorted by relevance

123456789

/linux/fs/btrfs/
H A Dprint-tree.h18 void btrfs_print_tree(const struct extent_buffer *c, bool follow);
H A Dprint-tree.c586 void btrfs_print_tree(const struct extent_buffer *c, bool follow) in btrfs_print_tree() argument
614 if (!follow) in btrfs_print_tree()
636 btrfs_print_tree(next, follow); in btrfs_print_tree()
/linux/scripts/
H A Ddev-needs.sh40 --exclude-devlinks Don't follow device links when tracking probe
125 # They can also have cycles. So, don't follow them.
/linux/tools/testing/selftests/lkdtm/
H A Dstack-entropy.sh24 dmesg --follow >"$log" & pid=$!
/linux/Documentation/bpf/
H A Dfs_kfuncs.rst16 To avoid recursions, these kfuncs follow the following rules:
/linux/Documentation/userspace-api/media/v4l/
H A Dvidioc-g-dv-timings.rst231 - The timings follow the CEA-861 Digital TV Profile standard
233 - The timings follow the VESA Discrete Monitor Timings standard
235 - The timings follow the VESA Coordinated Video Timings standard
237 - The timings follow the VESA Generalized Timings Formula standard
239 - The timings follow the SDI Timings standard.
H A Ddev-encoder.rst165 follow standard semantics.
191 follow standard semantics.
200 follow standard semantics.
217 follow standard semantics.
227 follow standard semantics.
389 follow standard semantics.
422 follow standard semantics.
549 configuration change to be allowed. To do this, it may follow the `Drain`
561 related ``CAPTURE`` buffers are given to the client, the client must follow the
/linux/fs/coda/
H A Dpioctl.c69 data.follow ? LOOKUP_FOLLOW : 0, &path); in coda_pioctl()
/linux/Documentation/ABI/testing/
H A Dsysfs-class-power-gaokun9 for delay hours, battery charging will follow the rules of
H A Dsysfs-platform-eeepc-laptop43 is defined as follow::
H A Dsysfs-platform-asus-laptop7 is composed by 4 bits and defined as follow::
H A Dsysfs-firmware-ofw15 path directly, but instead should follow /proc/device-tree
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dbrcm,bcm963xx-cfe-nor-partitions.txt4 Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
/linux/drivers/misc/ocxl/
H A DKconfig29 dedicated OpenCAPI link, and don't follow the same protocol.
/linux/Documentation/
H A DKconfig18 The files under Documentation/ABI should follow what's
/linux/Documentation/i2c/
H A Dslave-eeprom-backend.rst14 'slave-<type>[ro]'. Examples follow:
/linux/Documentation/admin-guide/
H A Dedid.rst11 either correctly working because all components follow the standards -
/linux/Documentation/filesystems/ext4/
H A Ddirectory.rst229 the leaf nodes that follow (in tree order) in case of hash collisions.
312 - Maximum number of dx_entries that can follow this header, plus 1 for
317 - Actual number of dx_entries that follow this header, plus 1 for the
384 - Maximum number of dx_entries that can follow this header, plus 1 for
389 - Actual number of dx_entries that follow this header, plus 1 for the
/linux/Documentation/tools/rv/
H A Drv-mon-sched.rst26 the scheduler should follow.
/linux/Documentation/process/
H A Dcoding-assistants.rst11 AI tools helping with Linux kernel development should follow the standard
64 When an AI assistant is used to find and fix bugs, it **MUST** follow at least
/linux/Documentation/hwmon/
H A Dlm77.rst35 * When setting a limit, its hysteresis will automatically follow, the
/linux/tools/build/Documentation/
H A DBuild.txt66 To follow the above example, the user provides following 'Build' files:
157 All existing '.cmd' files are included in the Build process to follow properly
/linux/tools/testing/selftests/sgx/
H A Dtest_encl_bootstrap.S53 # Entry point for dynamically created TCS page expected to follow
/linux/drivers/pci/hotplug/
H A DTODO38 * The various slot data structures are difficult to follow and need to be
/linux/Documentation/devicetree/bindings/remoteproc/
H A Dti,davinci-rproc.txt35 interrupts from the DSP. The value should follow the

123456789