Searched full:consequence (Results 1 – 25 of 142) sorted by relevance
123456
| /linux-6.14.4/Documentation/networking/ |
| D | ipsec.rst | 45 above scenario. The consequence of doing so is small packet(uncompressed)
|
| /linux-6.14.4/Documentation/hwmon/ |
| D | pc87360.rst | 137 measurement) one. As a consequence, these temperatures are exported as
181 which case cached values are returned instead). As a consequence, when
|
| /linux-6.14.4/tools/usb/usbip/ |
| D | COPYING | 197 7. If, as a consequence of a court judgment or allegation of patent
203 License and any other pertinent obligations, then as a consequence you
227 be a consequence of the rest of this License.
|
| /linux-6.14.4/LICENSES/preferred/ |
| D | GPL-2.0 | 216 7. If, as a consequence of a court judgment or allegation of patent
222 License and any other pertinent obligations, then as a consequence you
246 be a consequence of the rest of this License.
|
| D | LGPL-2.1 | 378 11. If, as a consequence of a court judgment or allegation of patent
384 License and any other pertinent obligations, then as a consequence you
408 be a consequence of the rest of this License.
|
| D | LGPL-2.0 | 358 11. If, as a consequence of a court judgment or allegation of patent
364 License and any other pertinent obligations, then as a consequence you
388 be a consequence of the rest of this License.
|
| /linux-6.14.4/Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhuv3.yaml | 40 As a consequence both blocks needs to be represented separately and specified
117 to generate interrupts; as a consequence it can expose a varying number of
|
| /linux-6.14.4/tools/perf/Documentation/ |
| D | intel-bts.txt | 10 consequence the present implementation is limited to per-thread recording.
|
| /linux-6.14.4/tools/memory-model/Documentation/ |
| D | locking.txt | 45 consequence that if the final value of r0 is equal to 1, then the final
77 This also has the consequence that if the final value of r1 is equal
|
| /linux-6.14.4/arch/m68k/amiga/ |
| D | chipram.c | 69 * allocate Chip RAM before kmalloc() is functional. As a consequence,
|
| /linux-6.14.4/arch/powerpc/lib/ |
| D | strlen_32.S | 30 * of no consequence since the least significant match is the one
|
| /linux-6.14.4/Documentation/admin-guide/pm/ |
| D | strategies.rst | 27 components of the system, as needed, in the working state. In consequence, if
|
| /linux-6.14.4/tools/testing/selftests/powerpc/stringloops/ |
| D | strlen_32.S | 30 * of no consequence since the least significant match is the one
|
| /linux-6.14.4/drivers/regulator/ |
| D | scmi-regulator.c | 11 // its users to operate upon: as a consequence the resulting operational
217 * voltages: as a consequence each levels_uv entry is guaranteed to in scmi_regulator_common_init()
|
| /linux-6.14.4/drivers/gpu/drm/i915/display/ |
| D | intel_vga.c | 92 * consequence, bind vgacon, we'll get stuck in an infinite loop at in intel_vga_reset_io_mem()
|
| /linux-6.14.4/Documentation/power/ |
| D | s2ram.rst | 78 Consequence is that after a resume (even if it is successful) your system
|
| /linux-6.14.4/drivers/misc/ |
| D | tps6594-esm.c | 45 * As a consequence, ESM can not be used on those PMIC. in tps6594_esm_probe()
|
| /linux-6.14.4/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that,
|
| /linux-6.14.4/Documentation/tools/rtla/ |
| D | rtla-hwnoise.rst | 22 of threads as a consequence, only non-maskable interrupts and hardware-related
|
| /linux-6.14.4/tools/testing/radix-tree/ |
| D | regression1.c | 12 * 3. The non-zero index item is deleted, and as a consequence the other item
|
| /linux-6.14.4/Documentation/block/ |
| D | bfq-iosched.rst | 106 of the background I/O workload. As a consequence, these applications
256 the maximum budget (slice) assigned to queues. As a consequence,
373 consequence of this behavior, and of further issues described for the
|
| /linux-6.14.4/block/ |
| D | bfq-wf2q.c | 59 * its turn, may change as a consequence of the insertion or
61 * sd. These insertions/extractions occur as a consequence of
189 * entity, even according to the above definition. As a consequence, a
881 * queues. As a consequence, the finish timestamps of all new in bfq_update_fin_time_enqueue()
1475 * service order in sd changed as a consequence of the in bfq_get_next_queue()
|
| /linux-6.14.4/tools/testing/selftests/arm64/signal/ |
| D | test_signals_utils.h | 140 * before the execution path is restored here: as a consequence in get_current_context()
|
| /linux-6.14.4/include/uapi/linux/ |
| D | rfkill.h | 154 * As a consequence, just recompiling with a new struct version caused
|
| /linux-6.14.4/drivers/i2c/busses/ |
| D | i2c-designware-amdpsp.c | 200 * set above. As a consequence consecutive calls to acquire will bypass in psp_acquire_i2c_bus()
|
123456