Searched refs:follow (Results 1 – 25 of 332) sorted by relevance
12345678910>>...14
| /Linux-v6.6/fs/btrfs/ |
| D | print-tree.h | 13 void btrfs_print_tree(const struct extent_buffer *c, bool follow);
|
| D | print-tree.c | 356 void btrfs_print_tree(const struct extent_buffer *c, bool follow) in btrfs_print_tree() argument
385 if (!follow) in btrfs_print_tree()
411 btrfs_print_tree(next, follow); in btrfs_print_tree()
|
| /Linux-v6.6/scripts/ |
| D | dev-needs.sh | 40 --exclude-devlinks Don't follow device links when tracking probe
125 # They can also have cycles. So, don't follow them.
|
| /Linux-v6.6/tools/testing/selftests/lkdtm/ |
| D | stack-entropy.sh | 24 dmesg --follow >"$log" & pid=$!
|
| /Linux-v6.6/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-dv-timings.rst | 231 - 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.
|
| D | dev-encoder.rst | 164 follow standard semantics.
190 follow standard semantics.
199 follow standard semantics.
216 follow standard semantics.
226 follow standard semantics.
388 follow standard semantics.
421 follow standard semantics.
548 configuration change to be allowed. To do this, it may follow the `Drain`
560 related ``CAPTURE`` buffers are given to the client, the client must follow the
|
| /Linux-v6.6/fs/coda/ |
| D | pioctl.c | 69 data.follow ? LOOKUP_FOLLOW : 0, &path); in coda_pioctl()
|
| /Linux-v6.6/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 52 Valid property sets must follow the guidance given by the Device Properties UUID
59 return property sets which do not follow that rule from _DSD in data packages
85 It often is useful to make _DSD return property sets that follow Device Tree
|
| /Linux-v6.6/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 4 Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
|
| /Linux-v6.6/Documentation/ |
| D | Kconfig | 18 The files under Documentation/ABI should follow what's
|
| /Linux-v6.6/Documentation/devicetree/bindings/spi/ |
| D | adi,axi-spi-engine.txt | 16 master. They follow the generic SPI bindings as outlined in spi-bus.txt.
|
| /Linux-v6.6/Documentation/process/ |
| D | maintainer-soc-clean-dts.rst | 10 SoC platforms or subarchitectures should follow all the rules from
|
| D | code-of-conduct-interpretation.rst | 97 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
|
| /Linux-v6.6/drivers/misc/ocxl/ |
| D | Kconfig | 29 dedicated OpenCAPI link, and don't follow the same protocol.
|
| /Linux-v6.6/Documentation/i2c/ |
| D | slave-eeprom-backend.rst | 14 'slave-<type>[ro]'. Examples follow:
|
| /Linux-v6.6/Documentation/devicetree/bindings/thermal/ |
| D | armada-thermal.txt | 15 follow the rules described in:
|
| /Linux-v6.6/drivers/staging/media/av7110/ |
| D | audio-set-id.rst | 49 AC3 and in [0xA0,0xA7] for LPCM. More specifications may follow for
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-platform-eeepc-laptop | 43 is defined as follow::
|
| /Linux-v6.6/Documentation/cdrom/ |
| D | packet-writing.rst | 58 However, some drives don't follow the specification and expect the
60 follow the specification, but suffer bad performance problems if the
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | gfs2-uevents.rst | 19 is successful, an ONLINE uevent will follow. If it is not successful
20 then a REMOVE uevent will follow.
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | lm77.rst | 35 * When setting a limit, its hysteresis will automatically follow, the
|
| /Linux-v6.6/Documentation/virt/kvm/ |
| D | review-checklist.rst | 7 1. The patch must follow Documentation/process/coding-style.rst and
|
| /Linux-v6.6/tools/build/Documentation/ |
| D | Build.txt | 66 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-v6.6/Documentation/dev-tools/ |
| D | ktap.rst | 58 Plan lines must follow the format of "1..N" where N is the number of tests or subtests.
59 Plan lines follow version lines to indicate the number of nested tests.
87 must follow a hash sign, "#".
171 There may be lines within KTAP output that do not follow the format of one of
|
| /Linux-v6.6/drivers/staging/media/ |
| D | Kconfig | 8 Most of them don't follow properly the V4L, DVB and/or RC API's,
|
12345678910>>...14
