| /linux/drivers/of/unittest-data/ |
| H A D | overlay_bad_add_dup_prop.dtso | 18 * will occur if the overlay is removed. Since the overlay apply
19 * fails, the memory leak does actually occur, and kmemleak will
|
| /linux/drivers/of/ |
| H A D | unittest.c | 2603 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_0()
2609 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_0()
2623 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_1()
2629 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_1()
2644 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_2()
2650 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_2()
2663 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_3()
2669 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_3()
2693 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_5()
2699 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_5()
[all …]
|
| /linux/Documentation/arch/arm/nwfpe/ |
| H A D | notes.rst | 5 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/arch/sparc/include/asm/ |
| H A D | estate.h | 15 * 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/arch/powerpc/include/uapi/asm/ |
| H A D | kvm_para.h | 14 * Additions to this struct must only occur at the end, and should be
55 * KVM, an exit must occur when changing the guest's MSR[PR].
|
| /linux/Documentation/sound/soc/ |
| H A D | pops-clicks.rst | 50 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/scripts/coccinelle/locks/ |
| H A D | double_lock.cocci | 2 /// 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/Documentation/userspace-api/gpio/ |
| H A D | gpio-v2-lineinfo-changed-read.rst | 50 The kernel timestamps events when they occur and stores them in a buffer
55 The buffer may overflow if bursts of events occur quicker than they are read
|
| H A D | gpio-lineinfo-changed-read.rst | 54 The kernel timestamps events when they occur and stores them in a buffer
59 The buffer may overflow if bursts of events occur quicker than they are read
|
| /linux/drivers/cpuidle/ |
| H A D | cpuidle-ux500.c | 42 /* 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/drivers/media/test-drivers/vicodec/ |
| H A D | codec-fwht.h | 39 * guaranteed not to occur in the compressed frame data. This header
52 * This sequence cannot occur in the encoded data
|
| /linux/net/x25/ |
| H A D | x25_timer.c | 95 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/drivers/gpu/drm/i915/ |
| H A D | Kconfig.profile | 59 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/drivers/net/wireless/intel/iwlwifi/fw/ |
| H A D | file.h | 919 * rx_ba_start: tid bitmap to configure on what tid the trigger should occur
921 * rx_ba_stop: tid bitmap to configure on what tid the trigger should occur
923 * tx_ba_start: tid bitmap to configure on what tid the trigger should occur
925 * tx_ba_stop: tid bitmap to configure on what tid the trigger should occur
927 * rx_bar: tid bitmap to configure on what tid the trigger should occur
929 * tx_bar: tid bitmap to configure on what tid the trigger should occur
931 * frame_timeout: tid bitmap to configure on what tid the trigger should occur
|
| /linux/net/ipv4/ |
| H A D | tcp_nv.c | 6 * 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/tools/testing/selftests/arm64/mte/ |
| H A D | check_buffer_fill.c | 118 /* 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/arch/powerpc/kernel/ |
| H A D | eeh_event.c | 19 * however, the recovery processing needs to occur asynchronously
33 * The detection of a frozen slot can occur inside an interrupt,
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | suspend-flows.rst | 15 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/arch/xtensa/kernel/ |
| H A D | vectors.S | 129 * Occasionally, the kernel expects a double exception to occur. This usually
133 * processing occurs. Also in kernel mode, TLB misses can occur if accessing
162 * - These registers must be saved before a double exception can occur.
560 * that may occur on a0 reload from stack. It may occur because
|
| /linux/drivers/gpu/drm/amd/include/ivsrcid/dcn/ |
| H A D | irqsrcs_dcn_1_0.h | 784 …HUBP0_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
787 …HUBP1_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
790 …HUBP2_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
793 …HUBP3_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
796 …HUBP4_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
799 …HUBP5_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
802 …HUBP6_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
805 …HUBP7_IHC_VM_CONTEXT_ERROR 0x23 // "Reports three types of fault that may occur during memory addr…
|
| /linux/kernel/trace/rv/monitors/opid/ |
| H A D | Kconfig | 12 Monitor to ensure operations like wakeup and need resched occur with
|
| /linux/tools/memory-model/Documentation/ |
| H A D | explanation.txt | 174 If this were to occur it would mean the driver contains a bug, because
176 happens, the LKMM does predict this outcome can occur, and the example
194 that the undesired result r1 = 1, r2 = 0 cannot occur. The reasoning
221 pattern cannot occur, but in other respects it differs from Sequential
246 this outcome to occur, and in fact it does sometimes occur on x86 and
258 (i.e., the order in which certain events occur) but it doesn't have to
262 as those instructions occur in the code, and there are many other
280 that outcome cannot occur.
308 write event is omitted for executions where it doesn't occur, such as
332 can think of it as the order in which statements occur in the source
[all …]
|
| /linux/tools/arch/mips/include/uapi/asm/ |
| H A D | kvm.h | 137 * COUNT_CTL.DC=1 will appear to occur at this time. When COUNT_CTL.DC is
145 * Specifies the rate of the CP0_Count timer in Hz. Modifications occur without
|
| /linux/drivers/watchdog/ |
| H A D | booke_wdt.c | 24 * trigger a watchdog timeout. This watchdog timeout will occur 3 times, the
26 * occur, and the final time the board will reset.
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-kvm.txt | 94 analyze events which occur on this vcpu. (default: all vcpus)
131 analyze events which occur on this vcpu. (default: all vcpus)
|