Searched full:avoided (Results 1 – 25 of 514) sorted by relevance
12345678910>>...21
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/ |
| D | ia_css_err.h | 30 This warning can be avoided by de-queuing ISYS buffers more timely. */
32 This warning can be avoided by de-queuing PSYS buffers more timely. */
34 This warning can be avoided by unlocking locked frame-buffers more timely. */
36 This warning can be avoided by unlocking locked frame-buffers more timely. */
38 This warning can be avoided by unlocking locked frame-buffers more timely. */
40 This warning can be avoided by providing a param set for each frame. */
|
| /kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/ |
| D | ia_css_err.h | 30 This warning can be avoided by de-queuing ISYS buffers more timely. */
32 This warning can be avoided by de-queuing PSYS buffers more timely. */
34 This warning can be avoided by unlocking locked frame-buffers more timely. */
36 This warning can be avoided by unlocking locked frame-buffers more timely. */
38 This warning can be avoided by unlocking locked frame-buffers more timely. */
40 This warning can be avoided by providing a param set for each frame. */
|
| /kernel/linux/linux-6.6/arch/x86/boot/compressed/ |
| D | kaslr.c | 179 * system can use. Region above the limit should be avoided. in parse_memmap()
311 * The mem_avoid array is used to store the ranges that need to be avoided
372 * (i.e. it does not include its run size). This range must be avoided
376 * range includes ZO's heap and stack, and must be avoided since it
379 * Since the above two ranges need to be avoided and they are adjacent,
429 * Does this memory vector overlap a known avoided area? If so, record the
|
| /kernel/linux/linux-5.10/arch/x86/boot/compressed/ |
| D | kaslr.c | 183 * system can use. Region above the limit should be avoided. in parse_memmap()
315 * The mem_avoid array is used to store the ranges that need to be avoided
376 * (i.e. it does not include its run size). This range must be avoided
380 * range includes ZO's heap and stack, and must be avoided since it
383 * Since the above two ranges need to be avoided and they are adjacent,
433 * Does this memory vector overlap a known avoided area? If so, record the
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | this_cpu_ops.rst | 121 lines can be avoided if multiple processors concurrently go through
307 unusual and should be avoided.
331 data within the same cache line are avoided. Also costly synchronization
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | this_cpu_ops.rst | 120 lines can be avoided if multiple processors concurrently go through
305 unusual and should be avoided.
329 data within the same cache line are avoided. Also costly synchronization
|
| /kernel/linux/linux-5.10/arch/s390/include/asm/ |
| D | vmlinux.lds.h | 12 * structs are avoided and linker produces consistent result.
|
| /kernel/linux/linux-6.6/arch/s390/include/asm/ |
| D | vmlinux.lds.h | 12 * structs are avoided and linker produces consistent result.
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | selection-api-vs-crop-api.rst | 25 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>`. Those operations should be avoided
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | page_frags.rst | 21 advantage to doing this is that multiple calls to get_page can be avoided
|
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | page_frags.rst | 19 advantage to doing this is that multiple calls to get_page can be avoided
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | selection-api-vs-crop-api.rst | 25 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>`. Those operations should be avoided
|
| /kernel/linux/linux-6.6/Documentation/virt/ |
| D | guest-halt-polling.rst | 15 2) The VM-exit cost can be avoided.
|
| /kernel/linux/linux-5.10/Documentation/virt/ |
| D | guest-halt-polling.rst | 15 2) The VM-exit cost can be avoided.
|
| /kernel/linux/linux-6.6/net/netfilter/ |
| D | xt_CHECKSUM.c | 62 …pr_warn_once("CHECKSUM should be avoided. If really needed, restrict with \"-p udp\" and only use… in checksum_tg_check()
|
| /kernel/linux/linux-5.10/net/netfilter/ |
| D | xt_CHECKSUM.c | 62 …pr_warn_once("CHECKSUM should be avoided. If really needed, restrict with \"-p udp\" and only use… in checksum_tg_check()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | brcm,bcm2711-hdmi.yaml | 83 avoided?
|
| /kernel/linux/linux-6.6/drivers/staging/vc04_services/interface/ |
| D | TODO | 24 variables avoided.
|
| /kernel/linux/linux-6.6/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 147 should be avoided almost all of the time.
167 understand, but it should absolutely be avoided. This is especially true
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/ |
| D | brcm,bcm2711-hdmi.yaml | 101 avoided?
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/touchscreen/ |
| D | ti,am3359-tsc.yaml | 53 avoided. The pen-up detection happens immediately after the charge step,
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/ |
| D | checkpatch.rst | 276 Architecture specific defines should be avoided wherever
286 BUG() or BUG_ON() should be avoided totally.
425 otherwise valid syscalls. This should be avoided in new code.
430 ENOTSUPP is not a standard error code and should be avoided in new patches.
649 side of the test should be avoided.
783 Local symbol names that are prefixed with `.L` should be avoided,
|
| /kernel/linux/linux-6.6/arch/x86/include/asm/fpu/ |
| D | xstate.h | 60 * be avoided. Such supervisor state components should only be saved/restored
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/fpu/ |
| D | xstate.h | 44 * be avoided. Such supervisor state components should only be saved/restored
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | designware-pcie.txt | 13 is deprecated and should be avoided.)
|
12345678910>>...21