Home
last modified time | relevance | path

Searched full:occur (Results 1 – 25 of 1334) sorted by relevance

12345678910>>...54

/Linux-v6.6/Documentation/admin-guide/
Dabi-testing.rst12 be aware of changes that can occur before these interfaces move to
17 developers can easily notify them if any changes occur.
/Linux-v6.6/drivers/of/unittest-data/
Doverlay_bad_add_dup_prop.dtso18 * will occur if the overlay is removed. Since the overlay apply
19 * fails, the memory leak does actually occur, and kmemleak will
/Linux-v6.6/Documentation/arch/arm/nwfpe/
Dnotes.rst5 been able to track it down yet. This does not occur with the emulator
20 then no conversion would occur. This has performance considerations. The
/Linux-v6.6/drivers/of/
Dunittest.c2226 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_0()
2232 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_0()
2246 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_1()
2252 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_1()
2267 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_2()
2273 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_2()
2286 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_3()
2292 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_3()
2316 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_5()
2322 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_5()
[all …]
/Linux-v6.6/arch/sparc/include/asm/
Destate.h15 * errors 2) uncorrectable E-cache errors. Such events only occur on reads
17 * fetches 3) atomic operations. Such events _cannot_ occur for: 1) merge
/Linux-v6.6/Documentation/sound/soc/
Dpops-clicks.rst50 An unwanted zipper noise can occur within the audio playback or capture stream
54 for each volume control. The ZC forces the gain change to occur when the signal
/Linux-v6.6/scripts/coccinelle/locks/
Ddouble_lock.cocci2 /// Find double locks. False positives may occur when some paths cannot
3 /// occur at execution, due to the values of variables, and when there is
/Linux-v6.6/arch/powerpc/include/uapi/asm/
Dkvm_para.h27 * Additions to this struct must only occur at the end, and should be
68 * KVM, an exit must occur when changing the guest's MSR[PR].
/Linux-v6.6/drivers/cpuidle/
Dcpuidle-ux500.c42 /* If an error occur, we will have to recouple the gic in ux500_enter_idle()
58 * not occur on the gic ... */ in ux500_enter_idle()
/Linux-v6.6/Documentation/ABI/
DREADME27 aware of changes that can occur before these interfaces move to
31 notify them if any changes occur (see the description of the
/Linux-v6.6/drivers/media/test-drivers/vicodec/
Dcodec-fwht.h39 * guaranteed not to occur in the compressed frame data. This header
52 * This sequence cannot occur in the encoded data
/Linux-v6.6/net/x25/
Dx25_timer.c95 if (sock_owned_by_user(sk)) /* can currently only occur in state 3 */ in x25_heartbeat_expiry()
163 if (sock_owned_by_user(sk)) { /* can currently only occur in state 3 */ in x25_timer_expiry()
/Linux-v6.6/drivers/gpu/drm/i915/
DKconfig.profile59 How long to wait (in milliseconds) for a preemption event to occur
77 How long to wait (in milliseconds) for a preemption event to occur
/Linux-v6.6/drivers/net/wireless/intel/iwlwifi/fw/
Dfile.h859 * rx_ba_start: tid bitmap to configure on what tid the trigger should occur
861 * rx_ba_stop: tid bitmap to configure on what tid the trigger should occur
863 * tx_ba_start: tid bitmap to configure on what tid the trigger should occur
865 * tx_ba_stop: tid bitmap to configure on what tid the trigger should occur
867 * rx_bar: tid bitmap to configure on what tid the trigger should occur
869 * tx_bar: tid bitmap to configure on what tid the trigger should occur
871 * frame_timeout: tid bitmap to configure on what tid the trigger should occur
/Linux-v6.6/Documentation/arch/ia64/
Dmca.rst9 MCA/INIT are completely asynchronous. They can occur at any time, when
118 violations (can occur at _any_ time) and they build from there.
140 about any registers having changed. MCA/INIT can occur while the cpu
/Linux-v6.6/include/linux/can/
Dbittiming.h25 * on the RX pin might occur on the previous bit.
73 * occur and the normal sampling point is used instead. The
/Linux-v6.6/arch/powerpc/kernel/
Deeh_event.c19 * however, the recovery processing needs to occur asynchronously
33 * The detection of a frozen slot can occur inside an interrupt,
/Linux-v6.6/net/ipv4/
Dtcp_nv.c6 * deal with the issues that occur in modern networks.
8 * the ability to detect congestion before packet losses occur.
9 * When congestion (queue buildup) starts to occur, TCP-NV
42 * nv_loss_dec_factor Decrease cwnd to this (80%) when losses occur
/Linux-v6.6/tools/testing/selftests/arm64/mte/
Dcheck_buffer_fill.c118 /* Imprecise fault should occur otherwise return error */ in check_buffer_underflow_by_byte()
136 /* Precise fault should occur otherwise return error */ in check_buffer_underflow_by_byte()
219 /* Imprecise fault should occur otherwise return error */ in check_buffer_overflow_by_byte()
237 /* Precise fault should occur otherwise return error */ in check_buffer_overflow_by_byte()
/Linux-v6.6/Documentation/devicetree/bindings/net/ieee802154/
Dmcr20a.txt9 can occur deadlocks while handling isr.
/Linux-v6.6/drivers/net/
DLICENSE.SRC15 expected. Although updates may occur, no commitment exists.
/Linux-v6.6/Documentation/admin-guide/pm/
Dsuspend-flows.rst15 transition to occur for this purpose, but the other sleep states, commonly
51 transition is about to occur and when the resume transition has finished.
104 the tick do not occur until the CPU is woken up by another interrupt source.
/Linux-v6.6/include/linux/
Dtty_ldisc.h67 * @tty. No other call into the line discipline for this tty will occur
99 * an %EIO error. Multiple read calls may occur in parallel and the ldisc
160 * calls into the ldisc code will occur.
/Linux-v6.6/arch/mips/include/asm/vdso/
Dprocessor.h14 * hardware (incorrectly) doesn't ensure that writes will eventually occur.
/Linux-v6.6/Documentation/admin-guide/aoe/
Dtodo.rst7 there are no other pages available, then deadlock may occur when a

12345678910>>...54