Home
last modified time | relevance | path

Searched full:avoided (Results 1 – 25 of 287) sorted by relevance

12345678910>>...12

/linux-6.12.1/drivers/staging/media/atomisp/pci/
Dia_css_err.h30 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. */
/linux-6.12.1/arch/x86/boot/compressed/
Dkaslr.c156 * system can use. Region above the limit should be avoided. in parse_memmap()
286 * The mem_avoid array is used to store the ranges that need to be avoided
347 * (i.e. it does not include its run size). This range must be avoided
351 * range includes ZO's heap and stack, and must be avoided since it
354 * Since the above two ranges need to be avoided and they are adjacent,
404 * Does this memory vector overlap a known avoided area? If so, record the
/linux-6.12.1/Documentation/core-api/
Dthis_cpu_ops.rst120 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
Dnetlink.rst17 but should be avoided in new families. The ``unspec`` enum values are
Dmemory-hotplug.rst98 Especially, there is a possible lock inversion that is avoided using
/linux-6.12.1/arch/s390/include/asm/
Dvmlinux.lds.h12 * structs are avoided and linker produces consistent result.
/linux-6.12.1/Documentation/mm/
Dpage_frags.rst19 advantage to doing this is that multiple calls to get_page can be avoided
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dselection-api-vs-crop-api.rst25 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>`. Those operations should be avoided
/linux-6.12.1/Documentation/virt/
Dguest-halt-polling.rst15 2) The VM-exit cost can be avoided.
/linux-6.12.1/net/netfilter/
Dxt_CHECKSUM.c62 …pr_warn_once("CHECKSUM should be avoided. If really needed, restrict with \"-p udp\" and only use… in checksum_tg_check()
/linux-6.12.1/Documentation/maintainer/
Drebasing-and-merging.rst147 should be avoided almost all of the time.
167 understand, but it should absolutely be avoided. This is especially true
/linux-6.12.1/Documentation/dev-tools/
Dcheckpatch.rst276 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,
/linux-6.12.1/Documentation/devicetree/bindings/input/touchscreen/
Dti,am3359-tsc.yaml53 avoided. The pen-up detection happens immediately after the charge step,
/linux-6.12.1/Documentation/devicetree/bindings/display/
Dbrcm,bcm2711-hdmi.yaml101 avoided?
/linux-6.12.1/arch/x86/include/asm/fpu/
Dxstate.h60 * be avoided. Such supervisor state components should only be saved/restored
/linux-6.12.1/Documentation/admin-guide/
Dreporting-regressions.rst229 Is it a regression, if the issue can be avoided by updating some software?
256 Luckily this middling almost always can be avoided, as key developers for the
274 A quick note while at it: these situations could be avoided, if people would
300 Note, sometimes regressions can't be avoided to make progress -- and the latter
/linux-6.12.1/net/ipv4/
Dtcp_plb.c89 * previously avoided with a sk_rethink_txhash() call at RTO time.
/linux-6.12.1/Documentation/devicetree/bindings/
Dsubmitting-patches.rst25 docs. Repeating "binding" again should also be avoided.
/linux-6.12.1/tools/testing/selftests/size/
Dget_size.c14 * It should be statically linked, with startup libs avoided. It uses
/linux-6.12.1/include/linux/
Delfcore.h28 * and the typedef forms have been avoided. This is mostly like
/linux-6.12.1/Documentation/PCI/
Dmsi-howto.rst181 should be avoided in favor of letting pci_alloc_irq_vectors() cap the
198 acquire the spinlock. Such deadlocks can be avoided by using
/linux-6.12.1/kernel/bpf/
Dmap_in_map.c120 * RCU tasks trace grace period can be avoided. in bpf_map_fd_put_ptr()
/linux-6.12.1/Documentation/i2c/busses/
Di2c-ali15x3.rst121 SMBus. Therefore the SMBus hangs can generally be avoided
/linux-6.12.1/arch/s390/appldata/
Dappldata_net_sum.c25 * This is accessed as binary data by z/VM. If changes to it can't be avoided,
Dappldata_mem.c28 * This is accessed as binary data by z/VM. If changes to it can't be avoided,

12345678910>>...12