| /linux/fs/btrfs/ |
| H A D | print-tree.h | 18 void btrfs_print_tree(const struct extent_buffer *c, bool follow);
|
| /linux/scripts/ |
| H A 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/tools/testing/selftests/lkdtm/ |
| H A D | stack-entropy.sh | 24 dmesg --follow >"$log" & pid=$!
|
| /linux/Documentation/bpf/ |
| H A D | fs_kfuncs.rst | 16 To avoid recursions, these kfuncs follow the following rules:
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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.
|
| H A D | dev-encoder.rst | 165 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 D | pioctl.c | 69 data.follow ? LOOKUP_FOLLOW : 0, &path); in coda_pioctl()
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A 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/Documentation/ABI/testing/ |
| H A D | sysfs-class-power-gaokun | 9 for delay hours, battery charging will follow the rules of
|
| H A D | sysfs-platform-eeepc-laptop | 43 is defined as follow::
|
| H A D | sysfs-platform-asus-laptop | 7 is composed by 4 bits and defined as follow::
|
| /linux/Documentation/devicetree/bindings/mtd/partitions/ |
| H A D | brcm,bcm963xx-cfe-nor-partitions.txt | 4 Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
|
| /linux/drivers/misc/ocxl/ |
| H A D | Kconfig | 29 dedicated OpenCAPI link, and don't follow the same protocol.
|
| /linux/Documentation/ |
| H A D | Kconfig | 18 The files under Documentation/ABI should follow what's
|
| /linux/Documentation/i2c/ |
| H A D | slave-eeprom-backend.rst | 14 'slave-<type>[ro]'. Examples follow:
|
| /linux/Documentation/admin-guide/ |
| H A D | edid.rst | 11 either correctly working because all components follow the standards -
|
| /linux/Documentation/tools/rv/ |
| H A D | rv-mon-sched.rst | 26 the scheduler should follow.
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | directory.rst | 229 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/hwmon/ |
| H A D | lm77.rst | 35 * When setting a limit, its hysteresis will automatically follow, the
|
| /linux/tools/build/Documentation/ |
| H A 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/tools/testing/selftests/sgx/ |
| H A D | test_encl_bootstrap.S | 53 # Entry point for dynamically created TCS page expected to follow
|
| /linux/drivers/pci/hotplug/ |
| H A D | TODO | 38 * The various slot data structures are difficult to follow and need to be
|
| /linux/Documentation/staging/ |
| H A D | lzo.rst | 31 Optionally depending on the opcode and operands, extra data may follow. These
75 are called under the assumption that a certain number of bytes follow
100 0..16 : follow regular instruction encoding, see below. It is worth
|
| /linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | ti,davinci-rproc.txt | 35 interrupts from the DSP. The value should follow the
|
| /linux/Documentation/translations/ |
| H A D | index.rst | 35 contributors - follow the evolution of the official documentation and they
|