Searched full:subsequently (Results 1 – 25 of 418) sorted by relevance
12345678910>>...17
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | debugfs-scmi-raw | 9 Any subsequently received response can be read from this same
24 Any subsequently received response can be read from this same
77 Any subsequently received response can be read from this same
101 Any subsequently received response can be read from this same
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/ |
| D | spec_operation.json | 16 …ned accesses (as defined by the actual instruction), even if they are subsequently issued as multi…
20 …ned accesses (as defined by the actual instruction), even if they are subsequently issued as multi…
24 …ned accesses (as defined by the actual instruction), even if they are subsequently issued as multi…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | spec_operation.json | 20 …ned accesses (as defined by the actual instruction), even if they are subsequently issued as multi…
24 …ned accesses (as defined by the actual instruction), even if they are subsequently issued as multi…
28 …ned accesses (as defined by the actual instruction), even if they are subsequently issued as multi…
|
| /kernel/linux/linux-5.10/Documentation/staging/ |
| D | speculation.rst | 44 value will subsequently be discarded, but the speculated load may affect
45 microarchitectural state which can be subsequently measured.
|
| /kernel/linux/linux-6.6/Documentation/staging/ |
| D | speculation.rst | 44 value will subsequently be discarded, but the speculated load may affect
45 microarchitectural state which can be subsequently measured.
|
| /kernel/linux/linux-6.6/Documentation/arch/arm64/ |
| D | kdump.rst | 8 it can be subsequently analyzed. In order to do this, a preliminarily
80 low memory reservation will be done subsequently.
|
| /kernel/linux/linux-6.6/scripts/ |
| D | subarch.include | 5 # SUBARCH is subsequently ignored.
|
| /kernel/linux/linux-5.10/scripts/ |
| D | subarch.include | 5 # SUBARCH is subsequently ignored.
|
| /kernel/linux/linux-6.6/drivers/peci/ |
| D | Kconfig | 24 responsible for creating auxiliary devices that can subsequently
|
| /kernel/linux/linux-6.6/drivers/mfd/ |
| D | simple-mfd-i2c.h | 17 * associated C file will be subsequently registered.
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| D | simple-mfd-i2c.c | 10 * represented by child nodes in Device Tree will be subsequently registered.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/crypto/ |
| D | st,stm32-cryp.yaml | 10 the STn8820 SoC introduced in 2007, and subsequently used in the U8500
|
| D | st,stm32-hash.yaml | 10 the STn8820 SoC introduced in 2007, and subsequently used in the U8500
|
| /kernel/linux/linux-5.10/arch/arm64/include/asm/ |
| D | suspend.h | 30 * returns, and the data would be subsequently corrupted by the call to the
|
| /kernel/linux/linux-6.6/arch/arm64/include/asm/ |
| D | suspend.h | 30 * returns, and the data would be subsequently corrupted by the call to the
|
| /kernel/linux/linux-5.10/tools/power/acpi/man/ |
| D | acpidump.8 | 15 Subsequently, they can be processed by utilities in the ACPICA package.
|
| /kernel/linux/linux-6.6/tools/power/acpi/man/ |
| D | acpidump.8 | 15 Subsequently, they can be processed by utilities in the ACPICA package.
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | frontend.json | 30 …he event will count MSROM startups for UOPS that are speculative, and subsequently cleared by bran…
|
| /kernel/linux/linux-5.10/Documentation/sound/soc/ |
| D | pops-clicks.rst | 12 depending on the audio usage and this can subsequently cause a small pop or
|
| D | overview.rst | 38 core and are subsequently matched and configured when the application
|
| /kernel/linux/linux-6.6/Documentation/sound/soc/ |
| D | pops-clicks.rst | 12 depending on the audio usage and this can subsequently cause a small pop or
|
| D | overview.rst | 38 core and are subsequently matched and configured when the application
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | zsmalloc.rst | 33 be mapped using zs_map_object() to get a usable pointer and subsequently
|
| /kernel/linux/linux-6.6/Documentation/crypto/ |
| D | intro.rst | 70 to receive and subsequently to use. The initialization API calls have
|
| /kernel/linux/linux-5.10/Documentation/crypto/ |
| D | intro.rst | 70 to receive and subsequently to use. The initialization API calls have
|
12345678910>>...17