Searched refs:sufficient (Results 1 – 25 of 171) sorted by relevance
1234567
| /Linux-v6.1/tools/memory-model/litmus-tests/ |
| D | MP+pooncerelease+poacquireonce.litmus | 7 * smp_load_acquire() provide sufficient ordering for the message-passing
|
| D | MP+fencewmbonceonce+fencermbonceonce.litmus | 7 * sufficient ordering for the message-passing pattern. However, it
|
| D | IRIW+fencembonceonces+OnceOnce.litmus | 7 * between each pairs of reads. In other words, is smp_mb() sufficient to
|
| D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 6 * This litmus test shows that a release-acquire chain, while sufficient
|
| D | README | 26 sufficient to cause two different reading processes to agree on
149 spin_lock() sufficient to make ordering apparent to accesses
157 Is the ordering provided by a release-acquire chain sufficient
|
| /Linux-v6.1/Documentation/ABI/stable/ |
| D | o2cb | 9 Users: ocfs2-tools. It's sufficient to mail proposed changes to
|
| /Linux-v6.1/Documentation/ABI/obsolete/ |
| D | o2cb | 10 Users: ocfs2-tools. It's sufficient to mail proposed changes to
|
| /Linux-v6.1/Documentation/ABI/removed/ |
| D | o2cb | 9 Users: ocfs2-tools. It's sufficient to mail proposed changes to
|
| /Linux-v6.1/arch/m68k/ifpsp060/src/ |
| D | README-SRC | 11 are sufficient and were generated from these source files by
|
| /Linux-v6.1/Documentation/userspace-api/media/dvb/ |
| D | fe-read-ber.rst | 38 access to the device is sufficient.
|
| D | fe-read-signal-strength.rst | 38 to the device is sufficient.
|
| D | fe-get-frontend.rst | 37 this command, read-only access to the device is sufficient.
|
| D | fe-read-snr.rst | 38 to the device is sufficient.
|
| D | fe-read-uncorrected-blocks.rst | 40 sufficient.
|
| /Linux-v6.1/Documentation/devicetree/bindings/sound/ |
| D | max98357a.txt | 16 It's observed that 5ms is sufficient.
|
| D | max98373.txt | 25 for the I/V sense data is not sufficient, the device can also be configured
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | vfio-pci-device-specific-driver-acceptance.rst | 28 Additionally, drivers should make an attempt to provide sufficient
|
| D | sm501.rst | 50 (unless sufficient contiguous memory can be provided for the old and new
|
| /Linux-v6.1/drivers/staging/media/deprecated/saa7146/av7110/ |
| D | video-get-event.rst | 63 specified as the wake-up condition. Read-only permissions are sufficient
|
| /Linux-v6.1/Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12057.txt | 41 "interrupt-parent" and "interrupts" are usually sufficient):
|
| /Linux-v6.1/Documentation/filesystems/ext4/ |
| D | checksums.rst | 19 encounters directory blocks that lack sufficient empty space to add a
|
| /Linux-v6.1/arch/m68k/ifpsp060/ |
| D | iskeleton.S | 162 | If the implementation provided by the 68060ISP is sufficient,
173 | If the implementation provided by the 68060ISP is sufficient,
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 15 By design, a FAN_FS_ERROR notification exposes sufficient information
|
| /Linux-v6.1/arch/x86/boot/ |
| D | header.S | 520 # per 32767 bytes of data is sufficient. To avoid problems internal to a
522 # is sufficient, to ensure that in the worst case the decompressed data for
|
| /Linux-v6.1/arch/arm/vfp/ |
| D | vfphw.S | 95 @ sufficient to determine that the hardware state is valid.
|
1234567
