Searched full:absolutely (Results 1 – 25 of 41) sorted by relevance
12
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 28 particular placement until it's absolutely necessary (the commit timeout
|
| /Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer_mmio.yaml | 41 strongly discouraged; fix your firmware unless absolutely impossible.
|
| D | arm,arch_timer.yaml | 64 strongly discouraged; fix your firmware unless absolutely impossible.
|
| /Documentation/arch/x86/ |
| D | entry_64.rst | 108 that absolutely need the more expensive check for the GS base - and we
|
| /Documentation/arch/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 | 128 function, and only then when you can be absolutely certain that the outputs
|
| /Documentation/mm/ |
| D | highmem.rst | 91 be absolutely sure to keep the use of the return address local to the
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 167 understand, but it should absolutely be avoided. This is especially true
|
| /Documentation/RCU/ |
| D | checklist.rst | 511 Note that it is absolutely *not* sufficient to wait for a grace
524 However, these barrier functions are absolutely *not* guaranteed
|
| D | whatisRCU.rst | 112 use much lighter-weight synchronization, in some cases, absolutely no
747 Note that rcu_read_lock() and rcu_read_unlock() do absolutely nothing.
750 And there is absolutely no way that rcu_read_lock() can possibly
|
| /Documentation/core-api/ |
| D | this_cpu_ops.rst | 286 unless absolutely necessary. Please consider using an IPI to wake up
|
| /Documentation/process/ |
| D | handling-regressions.rst | 656 Breaking a user workflow for a "bug" is absolutely the WORST reason
667 don't break users". Because "I fixed a bug" is absolutely NOT AN
673 other programs at all. It is absolutely required, because flag-days
|
| D | embargoed-hardware-issues.rst | 120 other factors and should be only used when absolutely necessary. Encrypted
|
| D | email-clients.rst | 156 If you absolutely must send patches as attachments instead of inlining
|
| D | coding-style.rst | 392 really is absolutely **zero** portably accessible information there.
767 means that you absolutely **have** to reference count all your uses.
|
| /Documentation/networking/ |
| D | sfp-phylink.rst | 227 absolutely necessary to change the MAC configuration. An example
|
| /Documentation/admin-guide/ |
| D | svga.rst | 72 absolutely insane PC design.
|
| /Documentation/devicetree/bindings/usb/ |
| D | snps,dwc3.yaml | 248 absolutely sure of it.
|
| /Documentation/bpf/ |
| D | bpf_devel_QA.rst | 254 it is absolutely necessary to add test cases to the BPF kernel
261 absolutely crucial to make sure future changes do not accidentally
|
| D | kfuncs.rst | 248 absolutely no ABI stability guarantees.
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 570 | Therefore, there absolutely must be a full memory barrier between the |
602 | absolutely no code in some kernel builds. This means that the |
612 | absolutely no code, RCU infers quiescent states only at special |
699 rcu_read_unlock() provide absolutely no ordering guarantees except
1151 However, there are algorithms that absolutely must see consistent data.
1154 it is absolutely forbidden to update a semaphore that has just been
1904 | Absolutely not!!! |
2159 #. If a CPU is in a portion of the kernel that is absolutely positively
|
| /Documentation/locking/ |
| D | locktypes.rst | 418 However, this approach should be used only where absolutely necessary.
|
| /Documentation/arch/arm64/ |
| D | arm-acpi.rst | 136 the kernel will not fail to boot unless it absolutely has no other choice.
|
| /Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 569 absolutely no guarantee whether a memory block can be offlined successfully.
|
12