Searched full:therefore (Results 1 – 25 of 2247) sorted by relevance
12345678910>>...90
| /Linux-v5.15/Documentation/networking/ |
| D | x25.rst | 15 I therefore decided to write the implementation such that as far as the
17 layer of the Linux kernel and therefore it did not concern itself with
18 implementation of LAPB. Therefore the LAPB modules would be called by
|
| /Linux-v5.15/Documentation/networking/device_drivers/hamradio/ |
| D | baycom.rst | 22 therefore it supports just about every bit bang modem on a
65 and can therefore be fed from the parallel port and does not require
89 but they are now true kernel network interfaces. Installation is therefore
143 a reasonable DCD algorithm in software. Therefore, if your radio
159 startup time. Therefore the baycom drivers subsequently won't be able to
160 access a serial port. You might therefore find it necessary to release
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | control-dependencies.txt | 5 do not support them. One purpose of this document is therefore to
12 Therefore, a load-load control dependency will not preserve ordering
91 have been applied. Therefore, if you need ordering in this example,
134 The compiler is therefore within its rights to transform the above code
144 is gone, and the barrier won't bring it back. Therefore, if you need
257 (*) Compilers do not understand control dependencies. It is therefore
|
| /Linux-v5.15/arch/arm64/kvm/ |
| D | inject_fault.c | 122 * VCPU therefore is not currently executing guest code.
138 * VCPU therefore is not currently executing guest code.
153 * VCPU therefore is not currently executing guest code.
174 * VCPU therefore is not currently executing guest code.
|
| /Linux-v5.15/drivers/pci/controller/dwc/ |
| D | Kconfig | 93 hardware and therefore the driver re-uses the DesignWare core
122 DesignWare hardware and therefore the driver re-uses the
134 on DesignWare hardware and therefore the driver re-uses the
191 DesignWare hardware and therefore the driver re-uses the
292 and therefore the driver re-uses the DesignWare core functions to
|
| /Linux-v5.15/include/crypto/ |
| D | xts.h | 15 * key consists of keys of equal size concatenated, therefore in xts_check_key()
32 * key consists of keys of equal size concatenated, therefore in xts_verify_key()
|
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | imx6qdl-dhcom-drc02.dtsi | 15 * Tx and Rx are routed to the DHCOM UART1 rts/cts pins. Therefore the micro SD
73 * DHCOM UART1 rts/cts pins. Therefore this UART have to use DHCOM GPIOs
115 * Therefore, they have been removed from the list below.
|
| /Linux-v5.15/arch/x86/include/uapi/asm/ |
| D | ldt.h | 19 * call is more for 32bit mode therefore.
34 * programs can pass uninitialized values here. Therefore, in
|
| /Linux-v5.15/tools/arch/sparc/include/asm/ |
| D | barrier_64.h | 10 * Therefore, if interrupts are disabled, the chip can hang forever.
24 * The branch has to be mispredicted for the bug to occur. Therefore, we put
|
| /Linux-v5.15/tools/power/cpupower/man/ |
| D | cpupower-monitor.1 | 95 left. Therefore there can be some inaccuracy when cores are in an idle
131 The registers are accessed via PCI and therefore can still be read out while
138 Therefore this counter can be used to verify whether the graphics' driver
|
| /Linux-v5.15/Documentation/dev-tools/ |
| D | testing-overview.rst | 32 KUnit tests therefore are best written against small, self-contained parts
60 kselftest is therefore suited well to tests of whole features, as these will
80 kernel to allow capturing coverage on a per-task level. It's therefore useful
|
| D | kasan.rst | 17 KASAN comes with low memory and performance overheads and, therefore, can be
22 validity checks before every memory access and, therefore, require a compiler
192 intended for use in production as a security mitigation. Therefore, it supports
255 to store memory tags associated with each 16-byte memory cell (therefore, it
322 accessed by the kernel. Therefore, KASAN only maps real shadow for certain
356 therefore be wasteful. Furthermore, to ensure that different mappings
384 therefore needs to be disabled.
|
| /Linux-v5.15/arch/sparc/include/asm/ |
| D | barrier_64.h | 8 * Therefore, if interrupts are disabled, the chip can hang forever.
22 * The branch has to be mispredicted for the bug to occur. Therefore, we put
|
| /Linux-v5.15/Documentation/devicetree/bindings/virtio/ |
| D | iommu.txt | 6 masters. Therefore, the PCI root complex that hosts the virtio-iommu
24 - DMA from the IOMMU device isn't managed by another IOMMU. Therefore the
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | vfio.rst | 67 Therefore, while for the most part an IOMMU may have device level
69 IOMMU API therefore supports a notion of IOMMU groups. A group is
71 system. Groups are therefore the unit of ownership used by VFIO.
126 This device is therefore in IOMMU group 26. This device is on the
127 pci bus, therefore the user will make use of vfio-pci to manage the
152 This device is behind a PCIe-to-PCI bridge [4]_, therefore we also
155 not currently have a host driver, therefore it's not required to
161 no capabilities on its own and is therefore expected to be set to
|
| /Linux-v5.15/Documentation/RCU/ |
| D | UP.rst | 46 Therefore, in this case, allowing call_rcu() to immediately invoke
109 list, and is therefore within an RCU read-side critical section.
110 Therefore, the called function has been invoked within an RCU
|
| /Linux-v5.15/drivers/scsi/pcmcia/ |
| D | nsp_message.c | 21 * therefore we should poll the scsi phase here to catch in nsp_message_in()
62 * therefore we should poll the scsi phase here to catch in nsp_message_out()
|
| /Linux-v5.15/include/linux/mtd/ |
| D | xip.h | 27 * obviously not be running from flash. The __xipram is therefore marking
70 #warning "your system will therefore be unresponsive when writing or erasing flash"
|
| /Linux-v5.15/Documentation/crypto/ |
| D | intro.rst | 19 Therefore, a cipher handle variable usually has the name "tfm". Besides
68 returned to the consumer. Therefore, please refer to all initialization
|
| /Linux-v5.15/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 27 This document therefore summarizes RCU's requirements, and can be
110 started after the synchronize_rcu() started, and must therefore also
111 load a value of one from ``x``. Therefore, the outcome:
249 optimizations could cause trouble. Therefore, we clearly need some way
570 | Therefore, there absolutely must be a full memory barrier between the |
646 guarantee. Therefore, the justification for adding a conditional
683 therefore all too easy to assume that RCU is guaranteeing more than it
805 | synchronize_rcu() completed. Therefore, the code following |
988 | Therefore, even in practice, RCU users must abide by the theoretical |
996 RCU implementation must abide by them. They therefore bear repeating:
[all …]
|
| /Linux-v5.15/Documentation/ |
| D | atomic_t.txt | 67 Therefore, an explicitly unsigned variant of the atomic ops is strictly
84 smp_store_release() respectively. Therefore, if you find yourself only using
143 reversible. Bitops are irreversible and therefore the modified value
184 subsequent. Therefore a fully ordered primitive is like having an smp_mb()
|
| /Linux-v5.15/Documentation/vm/damon/ |
| D | faq.rst | 13 programs including the kernel. Therefore, having a dependency on specific
26 Therefore, 'idle pages tracking' and 'perf mem' could provide a subset of
|
| /Linux-v5.15/Documentation/filesystems/ext4/ |
| D | allocators.rst | 14 up file rewrites significantly. Therefore, it is useful to reduce
40 here is that all the files in a directory might be related, therefore it
|
| /Linux-v5.15/arch/arm64/kernel/vdso/ |
| D | sigreturn.S | 28 * the sigcontext. Re-enabling the cfi directives here therefore needs to be
66 * instruction sequence to unwind from signal handlers. We cannot, therefore,
|
| /Linux-v5.15/arch/sparc/kernel/ |
| D | ktlb.S | 24 /* The kernel executes in context zero, therefore we do not
136 /* The kernel executes in context zero, therefore we do not
263 /* The kernel executes in context zero, therefore we do not
|
12345678910>>...90
