Searched full:explicitly (Results 1 – 25 of 2892) sorted by relevance
12345678910>>...116
| /kernel/linux/linux-6.6/tools/testing/selftests/riscv/vector/ |
| D | vstate_prctl.c | 131 /* Turn on next's vector explicitly and test */ in main()
136 /* Turn off next's vector explicitly and test */ in main()
141 /* Turn on next's vector explicitly and test inherit */ in main()
151 /* Turn off next's vector explicitly and test inherit */ in main()
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | instantiating-devices.rst | 8 reason, the kernel code must instantiate I2C devices explicitly. There are
103 Method 2: Instantiate the devices explicitly
111 you can instantiate your I2C devices explicitly. This is done by filling
183 explicitly. Instead, i2c-core will probe for such devices as soon as their
210 * I2C buses must now explicitly say which I2C driver classes can probe
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | err.h | 45 * ERR_CAST - Explicitly cast an error-valued pointer to another pointer type
48 * Explicitly cast an error-valued pointer to another pointer type in such a
|
| /kernel/linux/linux-6.6/Documentation/i2c/ |
| D | instantiating-devices.rst | 8 reason, the kernel code must instantiate I2C devices explicitly. There are
107 Method 2: Instantiate the devices explicitly
115 you can instantiate your I2C devices explicitly. This is done by filling
191 explicitly. Instead, i2c-core will probe for such devices as soon as their
218 * I2C buses must now explicitly say which I2C driver classes can probe
|
| /kernel/linux/linux-5.10/arch/nds32/kernel/vdso/ |
| D | vdso.lds.S | 46 * We must supply the ELF program headers explicitly to get just one
47 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/arch/arm64/kernel/vdso32/ |
| D | vdso.lds.S | 53 * We must supply the ELF program headers explicitly to get just one
54 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/arch/x86/um/vdso/ |
| D | vdso-layout.lds.S | 56 * We must supply the ELF program headers explicitly to get just one
57 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/tools/include/linux/ |
| D | err.h | 64 * ERR_CAST - Explicitly cast an error-valued pointer to another pointer type
67 * Explicitly cast an error-valued pointer to another pointer type in such a
|
| /kernel/linux/linux-6.6/tools/include/linux/ |
| D | err.h | 64 * ERR_CAST - Explicitly cast an error-valued pointer to another pointer type
67 * Explicitly cast an error-valued pointer to another pointer type in such a
|
| /kernel/linux/linux-6.6/arch/x86/um/vdso/ |
| D | vdso-layout.lds.S | 56 * We must supply the ELF program headers explicitly to get just one
57 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/arch/riscv/kernel/vdso/ |
| D | vdso.lds.S | 48 * We must supply the ELF program headers explicitly to get just one
49 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-6.6/arch/arm/vdso/ |
| D | vdso.lds.S | 57 * We must supply the ELF program headers explicitly to get just one
58 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/arch/arm/vdso/ |
| D | vdso.lds.S | 57 * We must supply the ELF program headers explicitly to get just one
58 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/arch/mips/loongson2ef/ |
| D | Platform | 27 # Avoid this by explicitly disabling that assembler behaviour. If upstream
48 # support being enabled alongside -msoft-float. Thus explicitly disable MMI.
|
| /kernel/linux/linux-5.10/arch/sh/kernel/vsyscall/ |
| D | vsyscall.lds.S | 61 * We must supply the ELF program headers explicitly to get just one
62 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 9 exist until explicitly acknowledged to firmware.
18 but not explicitly acknowledged them to firmware and
|
| /kernel/linux/linux-5.10/arch/sparc/vdso/ |
| D | vdso-layout.lds.S | 89 * We must supply the ELF program headers explicitly to get just one
90 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-6.6/arch/sh/kernel/vsyscall/ |
| D | vsyscall.lds.S | 61 * We must supply the ELF program headers explicitly to get just one
62 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-6.6/arch/arm64/kernel/vdso32/ |
| D | vdso.lds.S | 72 * We must supply the ELF program headers explicitly to get just one
73 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-6.6/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 9 exist until explicitly acknowledged to firmware.
18 but not explicitly acknowledged them to firmware and
|
| /kernel/linux/linux-6.6/arch/riscv/kernel/vdso/ |
| D | vdso.lds.S | 59 * We must supply the ELF program headers explicitly to get just one
60 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/arch/arm64/kernel/vdso/ |
| D | vdso.lds.S | 67 * We must supply the ELF program headers explicitly to get just one
68 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-6.6/arch/sparc/vdso/ |
| D | vdso-layout.lds.S | 89 * We must supply the ELF program headers explicitly to get just one
90 * PT_LOAD segment, and set the flags explicitly to make segments read-only.
|
| /kernel/linux/linux-5.10/drivers/base/firmware_loader/ |
| D | Kconfig | 89 The uevent can be suppressed if the driver explicitly requested it,
114 driver which explicitly relies on this fallback mechanism. Only two
148 to be used for all firmware requests which explicitly do not disable a
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | blkzoned.h | 43 * @BLK_ZONE_COND_IMP_OPEN: The zone is open, but not explicitly opened.
44 * @BLK_ZONE_COND_EXP_OPEN: The zones was explicitly opened by an
46 * @BLK_ZONE_COND_CLOSED: The zone was [explicitly] closed after writing.
|
12345678910>>...116