Searched full:principle (Results 1 – 25 of 284) sorted by relevance
12345678910>>...12
| /kernel/linux/linux-6.6/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 12 namespace. In principle, the format of the data may be arbitrary, but it has to
66 principle, the property set may still not be regarded as a valid one.
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 12 namespace. In principle, the format of the data may be arbitrary, but it has to
62 principle, the property set may still not be regarded as a valid one.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/pm/ |
| D | cpuidle.rst | 26 situation in principle, so it may be necessary to find the most suitable one
32 principle, so the generic code that in principle need not depend on the hardware
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| D | cpuidle.rst | 26 situation in principle, so it may be necessary to find the most suitable one
32 principle, so the generic code that in principle need not depend on the hardware
|
| /kernel/linux/linux-6.6/tools/include/linux/ |
| D | err.h | 21 * The same principle works for userspace, because 'error' pointers
|
| /kernel/linux/linux-5.10/tools/include/linux/ |
| D | err.h | 21 * The same principle works for userspace, because 'error' pointers
|
| /kernel/linux/linux-6.6/arch/arm64/include/asm/ |
| D | mmu.h | 35 * may use a stale ASID. This is fine in principle as the new ASID is
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/ |
| D | no_new_privs.rst | 60 available to unprivileged tasks if ``no_new_privs`` is set. In principle,
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/ |
| D | no_new_privs.rst | 60 available to unprivileged tasks if ``no_new_privs`` is set. In principle,
|
| /kernel/linux/linux-6.6/arch/x86/entry/ |
| D | entry_64_compat.S | 30 * The SYSENTER instruction, in principle, should *only* occur in the
146 * The SYSCALL instruction, in principle, should *only* occur in the
|
| /kernel/linux/linux-6.6/lib/ |
| D | rcuref.c | 36 * In principle it should be possible to make refcount use the rcuref
99 * the working principle. The rest is left to the imagination of the
|
| /kernel/linux/linux-5.10/arch/arm64/include/asm/ |
| D | mmu.h | 37 * may use a stale ASID. This is fine in principle as the new ASID is
|
| /kernel/linux/linux-5.10/Documentation/misc-devices/ |
| D | bh1770glc.rst | 22 interface and interrupt logic. In principle they can run on their own,
|
| /kernel/linux/linux-6.6/Documentation/misc-devices/ |
| D | bh1770glc.rst | 22 interface and interrupt logic. In principle they can run on their own,
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | swsusp-and-swap-files.rst | 16 In principle the location of a swap file's header may be determined with the
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | swsusp-and-swap-files.rst | 16 In principle the location of a swap file's header may be determined with the
|
| /kernel/linux/linux-5.10/drivers/rtc/ |
| D | rtc-sa1100.c | 222 * In principle, the same problem would apply to bit 0, although it has in sa1100_rtc_init()
231 * initialization is unknown and could in principle happen during in sa1100_rtc_init()
|
| /kernel/linux/linux-6.6/drivers/rtc/ |
| D | rtc-sa1100.c | 222 * In principle, the same problem would apply to bit 0, although it has in sa1100_rtc_init()
231 * initialization is unknown and could in principle happen during in sa1100_rtc_init()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 13 The general principle of the naming scheme for Secure world bindings
|
| /kernel/linux/linux-5.10/arch/arm64/lib/ |
| D | strlen.S | 53 * NUL detection works on the principle that (X - 1) & (~X) & 0x80
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_sa.c | 33 * after the last allocated bo. Principle is that in a linear GPU ring
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 13 The general principle of the naming scheme for Secure world bindings
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 38 in principle, they should work in any architecture where these
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 38 in principle, they should work in any architecture where these
|
| /kernel/linux/linux-6.6/rust/ |
| D | helpers.c | 11 * exported, in principle. However, in general, the Rust compiler does not
|
12345678910>>...12