Searched full:absolutely (Results 1 – 25 of 35) sorted by relevance
12
| /Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer.yaml | 47 strongly discouraged; fix your firmware unless absolutely impossible.
|
| D | arm,arch_timer_mmio.yaml | 39 strongly discouraged; fix your firmware unless absolutely impossible.
|
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 28 particular placement until it's absolutely necessary (the commit timeout
|
| /Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 38 * unless absolutely necessary.
|
| /Documentation/x86/ |
| D | entry_64.rst | 108 that absolutely need the more expensive check for the GS base - and we
|
| /Documentation/devicetree/bindings/usb/ |
| D | dwc3.txt | 79 CAUTION: use only if you are absolutely sure of it.
|
| /Documentation/arm/ |
| D | interrupts.rst | 126 absolutely necessary.
|
| /Documentation/admin-guide/laptops/ |
| D | sonypi.rst | 157 *absolutely no guarantee* that this driver will not crash your
|
| /Documentation/security/ |
| D | siphash.rst | 127 then when you can be absolutely certain that the outputs will never be
|
| /Documentation/networking/ |
| D | sfp-phylink.rst | 214 absolutely necessary to change the MAC configuration. An example
|
| /Documentation/RCU/ |
| D | checklist.txt | 437 it is absolutely -not- sufficient to wait for a grace period!
448 However, these barrier functions are absolutely -not- guaranteed
|
| D | whatisRCU.txt | 91 use much lighter-weight synchronization, in some cases, absolutely no
667 Note that rcu_read_lock() and rcu_read_unlock() do absolutely nothing.
670 And there is absolutely no way that rcu_read_lock() can possibly
|
| D | rcubarrier.txt | 20 given that readers might well leave absolutely no trace of their
|
| /Documentation/ |
| D | this_cpu_ops.txt | 288 unless absolutely necessary. Please consider using an IPI to wake up
|
| D | DMA-API.txt | 12 machines. Unless you know that your driver absolutely has to support
|
| D | DMA-API-HOWTO.txt | 461 If you absolutely cannot know the direction of the DMA transfer,
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 167 understand, but it should absolutely be avoided. This is especially true
|
| /Documentation/process/ |
| D | email-clients.rst | 151 If you absolutely must send patches as attachments instead of inlining
|
| D | embargoed-hardware-issues.rst | 115 other factors and should be only used when absolutely necessary. Encrypted
|
| D | maintainer-pgp-guide.rst | 210 It is absolutely essential that your private keys are protected by a
907 important to keep in mind that there is absolutely no guarantee that the
|
| D | coding-style.rst | 351 really is absolutely **zero** portably accessible information there.
699 means that you absolutely **have** to reference count all your uses.
|
| /Documentation/admin-guide/ |
| D | svga.rst | 71 absolutely insane PC design.
|
| /Documentation/bpf/ |
| D | bpf_devel_QA.rst | 228 it is absolutely necessary to add test cases to the BPF kernel
235 absolutely crucial to make sure future changes do not accidentally
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.html | 734 Therefore, there absolutely must be a full memory barrier between the
787 generate absolutely no code in some kernel builds.
798 generate absolutely no code, RCU infers quiescent states only at
909 <tt>rcu_read_unlock()</tt> provide absolutely no ordering guarantees
1459 However, there are algorithms that absolutely must see consistent data.
1462 but it is absolutely forbidden to update a semaphore that has just been
2396 Absolutely not!!!
2744 <li> If a CPU is in a portion of the kernel that is absolutely
|
| /Documentation/arm64/ |
| D | arm-acpi.rst | 135 the kernel will not fail to boot unless it absolutely has no other choice.
|
12