Searched full:therefore (Results 1 – 25 of 3621) sorted by relevance
12345678910>>...145
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | baycom.txt | 17 therefore it supports just about every bit bang modem on a
59 and can therefore be fed from the parallel port and does not require
81 but they are now true kernel network interfaces. Installation is therefore
131 a reasonable DCD algorithm in software. Therefore, if your radio
145 startup time. Therefore the baycom drivers subsequently won't be able to
146 access a serial port. You might therefore find it necessary to release
|
| D | x25.txt | 11 I therefore decided to write the implementation such that as far as the
13 layer of the Linux kernel and therefore it did not concern itself with
14 implementation of LAPB. Therefore the LAPB modules would be called by
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-4.19/include/crypto/ |
| D | xts.h | 19 * key consists of keys of equal size concatenated, therefore in xts_check_key()
41 * key consists of keys of equal size concatenated, therefore in xts_verify_key()
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/arch/arm64/kvm/ |
| D | inject_fault.c | 177 * VCPU therefore is not currently executing guest code.
193 * VCPU therefore is not currently executing guest code.
208 * VCPU therefore is not currently executing guest code.
229 * VCPU therefore is not currently executing guest code.
|
| /kernel/linux/linux-4.19/arch/arm64/kvm/ |
| D | inject_fault.c | 187 * VCPU therefore is not currently executing guest code.
203 * VCPU therefore is not currently executing guest code.
217 * VCPU therefore is not currently executing guest code.
238 * VCPU therefore is not currently executing guest code.
|
| /kernel/linux/linux-5.10/drivers/pci/controller/dwc/ |
| D | Kconfig | 117 DesignWare hardware and therefore the driver re-uses the
129 on DesignWare hardware and therefore the driver re-uses the
185 DesignWare hardware and therefore the driver re-uses the
247 and therefore the driver re-uses the DesignWare core functions to
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | UP.txt | 44 Therefore, in this case, allowing call_rcu() to immediately invoke
102 list, and is therefore within an RCU read-side critical section.
103 Therefore, the called function has been invoked within an RCU
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | vfio.txt | 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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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"
|
12345678910>>...145