Searched refs:rely (Results 1 – 25 of 165) sorted by relevance
1234567
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-devices | 11 Please do not rely on the format of this tree because of
13 the tree, please use the /sys/class structure and rely
16 Or rely on the uevent messages to notify programs of
|
| /Linux-v5.10/drivers/input/mouse/ |
| D | maplemouse.c | 29 int buttons, relx, rely, relz; in dc_mouse_callback() local
37 rely = *(unsigned short *)(res + 14) - 512; in dc_mouse_callback()
44 input_report_rel(dev, REL_Y, rely); in dc_mouse_callback()
|
| /Linux-v5.10/fs/notify/dnotify/ |
| D | Kconfig | 9 superior alternatives, but some applications may still rely on
|
| /Linux-v5.10/Documentation/ABI/ |
| D | README | 26 programs can start to rely on these interfaces, but they must be
88 - Kconfig. Userspace should not rely on the presence or absence of any
93 - Kernel-internal symbols. Do not rely on the presence, absence, location, or
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | abi-testing.rst | 11 Userspace programs can start to rely on these interfaces, but they must
|
| /Linux-v5.10/tools/bpf/bpftool/Documentation/ |
| D | common_options.rst | 10 pids associated to BPF objects may rely on it).
|
| /Linux-v5.10/Documentation/arm/ |
| D | swp_emulation.rst | 23 when accessing uncached shared regions, LDREX/STREX rely on an external
|
| D | kernel_mode_neon.rst | 7 * Use only NEON instructions, or VFP instructions that don't rely on support
68 Earlier versions of VFP (prior to version 3) rely on software support for things
|
| D | mem_alignment.rst | 13 Of course this is a bad idea to rely on the alignment trap to perform
|
| /Linux-v5.10/Documentation/devicetree/bindings/mmc/ |
| D | sdhci-atmel.txt | 16 - assigned-clock-rates The rate of "multclk" in order to not rely on the
|
| /Linux-v5.10/fs/sysfs/ |
| D | Kconfig | 16 Some system agents rely on the information in sysfs to operate.
|
| /Linux-v5.10/arch/arm64/boot/dts/amlogic/ |
| D | meson-g12b-a311d-khadas-vim3.dts | 29 * testing purposes, but instead rely on the firmware/bootloader to
|
| D | meson-g12b-s922x-khadas-vim3.dts | 29 * testing purposes, but instead rely on the firmware/bootloader to
|
| D | meson-sm1-khadas-vim3l.dts | 84 * testing purposes, but instead rely on the firmware/bootloader to
|
| /Linux-v5.10/Documentation/accounting/ |
| D | cgroupstats.rst | 21 NOTE: We currently rely on delay accounting for extracting information
|
| /Linux-v5.10/Documentation/features/sched/membarrier-sync-core/ |
| D | arch-support.txt | 23 # Given that neither SYSRET{L,Q}, nor SYSEXIT, are core serializing, we rely
|
| /Linux-v5.10/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-dump | 21 Do not rely on any particular size of dump
|
| /Linux-v5.10/Documentation/power/ |
| D | apm-acpi.rst | 26 Both APM and ACPI rely on user-space daemons, apmd and acpid
|
| /Linux-v5.10/drivers/media/v4l2-core/ |
| D | Kconfig | 39 Only useful if you rely on the old behavior and use mknod instead of udev.
|
| /Linux-v5.10/Documentation/i2c/ |
| D | fault-codes.rst | 22 to respond correctly. Other code may need to rely on YOUR code reporting
57 host. Note that even if PECs are in use, you should not rely
|
| D | summary.rst | 21 achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
|
| /Linux-v5.10/Documentation/arm64/ |
| D | tagged-pointers.rst | 57 signal handlers in applications making use of tags cannot rely on the
|
| D | perf.rst | 60 exclusively rely on the PMU's hardware exception filtering - therefore we
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | ceph.rst | 25 In contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely
138 must rely on TCP's error correction to detect data corruption
|
| /Linux-v5.10/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 64 that rely on certain process-spawning semantics in Linux.
117 once we have the policy checking code in place, which will rely on GID policy
|
1234567
