Home
last modified time | relevance | path

Searched full:_any_ (Results 1 – 24 of 24) sorted by relevance

/linux-6.14.4/tools/testing/selftests/bpf/progs/
Dxdp_metadata2.c18 /* Call _any_ metadata function to make sure we don't crash. */ in freplace_rx()
/linux-6.14.4/arch/riscv/include/asm/
Dinsn.h265 /* special case to catch _any_ system instruction */
271 /* special case to catch _any_ branch instruction */
/linux-6.14.4/Documentation/locking/
Dspinlocks.rst87 Also, you cannot "upgrade" a read-lock to a write-lock, so if you at _any_
Dlockdep-design.rst188 could interrupt _any_ of the irq-unsafe or hardirq-unsafe locks, which
/linux-6.14.4/drivers/gpu/drm/amd/display/include/
Dlink_service_types.h239 * _ONLY_ be filled out from DM and then passed to DC, do NOT use these for _any_ kind of atomic
/linux-6.14.4/lib/
Dtest_linear_ranges.c36 * actually find _any_ bug from code in such environment and try fixing it...
/linux-6.14.4/scripts/coccinelle/api/
Dstream_open.cocci80 // file_operations + whether they have _any_ .read, .write, .llseek ... at all.
/linux-6.14.4/tools/testing/selftests/kvm/x86/
Dxapic_state_test.c240 * KVM_RUN and AVIC is disabled if _any_ vCPU is allowed to use x2APIC. in main()
Dpmu_counters_test.c145 * compiler can't insert _any_ code into the measured sequence. Note, ECX
/linux-6.14.4/Documentation/core-api/
Dmemory-allocation.rst94 * ``GFP_KERNEL & ~__GFP_RECLAIM`` - optimistic allocation without _any_
/linux-6.14.4/drivers/acpi/
Dprocessor_thermal.c27 * _any_ cpufreq driver and not only the acpi-cpufreq driver.
/linux-6.14.4/Documentation/devicetree/bindings/opp/
Dopp-v2-base.yaml170 A>, <sub-group B>, etc. The OPP will be enabled if _any_ of these
/linux-6.14.4/fs/ocfs2/
Ddcache.c136 * parent. ocfs2_dentry_attach_lock() wants to find _any_ alias as it
/linux-6.14.4/Documentation/admin-guide/
Dsvga.rst168 Allows to set _any_ BIOS mode including graphic ones and forcing specific
/linux-6.14.4/kernel/printk/
Dprintk_ringbuffer.h214 * report the existence of a record for _any_ given sequence number at all
/linux-6.14.4/drivers/hwmon/
Di5k_amb.c74 * are _any_ DIMMs in the channel. Attempting to read from
/linux-6.14.4/drivers/net/wan/
Dhd64572.h45 /* Register Access Macros (chan is 0 or 1 in _any_ case) */
/linux-6.14.4/fs/jffs2/
Dwbuf.c56 /* If ino == 0, _any_ non-GC writes mean 'yes' */ in jffs2_wbuf_pending_for_ino()
699 If ino arg is zero, do it if _any_ real (i.e. not GC) writes are
/linux-6.14.4/arch/x86/kvm/svm/
Davic.c507 * if _any_ targets are invalid, e.g. if the logical mode mask in avic_incomplete_ipi_interception()
/linux-6.14.4/drivers/md/
Ddm-table.c1437 * Cases requiring _any_ underlying device supporting some kind of attribute,
/linux-6.14.4/tools/lib/bpf/
Dbtf_dump.c2364 /* check all elements; if _any_ element is nonzero, all in btf_dump_type_data_check_zero()
/linux-6.14.4/drivers/net/ethernet/chelsio/cxgb4vf/
Dsge.c2636 * with _any_ configuration. Practice is different ... in t4vf_sge_init()
/linux-6.14.4/io_uring/
Dio_uring.c34 * io_uring also uses READ/WRITE_ONCE() for _any_ store or load that happens
/linux-6.14.4/kernel/sched/
Dcore.c10103 * The "10% effect" is relative and cumulative: from _any_ nice level,