Searched refs:occur (Results 1 – 25 of 209) sorted by relevance
123456789
| /Linux-v5.4/scripts/coccinelle/locks/ |
| 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-v5.4/Documentation/arm/nwfpe/ |
| 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-v5.4/Documentation/sound/soc/ |
| 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-v5.4/Documentation/devicetree/bindings/net/ieee802154/ |
| D | mcr20a.txt | 9 can occur deadlocks while handling isr.
|
| D | at86rf230.txt | 10 can occur deadlocks while handling isr.
|
| /Linux-v5.4/Documentation/driver-api/serial/ |
| D | tty.rst | 44 discipline for this tty will occur until it
60 No further calls into the ldisc code will occur.
64 the line. Multiple read calls may occur in parallel
85 calls. Multiple poll calls may occur in parallel.
90 ioctl calls may occur in parallel. May sleep.
94 Multiple ioctl calls may occur in parallel.
278 sleep. May occur in parallel in special cases.
|
| /Linux-v5.4/drivers/staging/unisys/ |
| D | TODO | 8 when they occur
|
| /Linux-v5.4/drivers/staging/fwserial/ |
| D | TODO | 5 conditions occur.
|
| /Linux-v5.4/drivers/net/ |
| D | LICENSE.SRC | 15 expected. Although updates may occur, no commitment exists.
|
| /Linux-v5.4/Documentation/admin-guide/aoe/ |
| D | todo.rst | 7 there are no other pages available, then deadlock may occur when a
|
| /Linux-v5.4/arch/sparc/kernel/ |
| D | wof.S | 97 save %g0, %g0, %g0 ! Go where saving will occur
144 save %g0, %g0, %g0 ! Go to where the saving will occur
|
| D | wuf.S | 295 andcc %twin_tmp2, 0x2, %g0 ! did fault occur?
|
| /Linux-v5.4/drivers/net/wireless/broadcom/brcm80211/ |
| D | Kconfig | 32 you when wireless problems occur.
|
| /Linux-v5.4/Documentation/ABI/ |
| D | README | 27 aware of changes that can occur before these interfaces move to
31 notify them if any changes occur (see the description of the
|
| /Linux-v5.4/Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 9 occur when tasks share some namespace (the columns) while living
|
| /Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | vctrl.txt | 22 voltage. On larger voltage decreases this can occur
|
| /Linux-v5.4/arch/arm/nwfpe/ |
| D | fpmodule.inl | 27 that caused the invalid instruction trap to occur. We adjust
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-kvm.txt | 103 analyze events which occur on this vcpu. (default: all vcpus)
137 analyze events which occur on this vcpu. (default: all vcpus)
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 30 soft-dirty bits clear, the #PF-s that occur after that are processed fast.
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | battery.txt | 11 behavior should a replacement that changes the battery type occur
|
| /Linux-v5.4/Documentation/ia64/ |
| D | mca.rst | 9 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-v5.4/Documentation/block/ |
| D | deadline-iosched.rst | 67 Front merges may still occur due to the cached last_merge hint, but since
|
| /Linux-v5.4/Documentation/usb/ |
| D | iuu_phoenix.rst | 14 occur and your system may freeze. As far I now,
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-edac | 117 to it. With this label in the module, when errors occur
125 must occur in userland at this time.
|
| /Linux-v5.4/tools/memory-model/Documentation/ |
| D | explanation.txt | 173 If this were to occur it would mean the driver contains a bug, because
175 happens, the LKMM does predict this outcome can occur, and the example
193 that the undesired result r1 = 1, r2 = 0 cannot occur. The reasoning
220 pattern cannot occur, but in other respects it differs from Sequential
245 this outcome to occur, and in fact it does sometimes occur on x86 and
257 (i.e., the order in which certain events occur) but it doesn't have to
261 as those instructions occur in the code, and there are many other
279 that outcome cannot occur.
307 write event is omitted for executions where it doesn't occur, such as
331 can think of it as the order in which statements occur in the source
[all …]
|
123456789
