| /openbmc/linux/Documentation/admin-guide/ |
| H A D | abi-testing.rst | 12 be aware of changes that can occur before these interfaces move to
17 developers can easily notify them if any changes occur.
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/linux/drivers/of/ |
| H A D | unittest.c | 2258 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_0()
2264 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_0()
2278 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_1()
2284 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_1()
2299 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_2()
2305 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_2()
2318 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_3()
2324 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_3()
2348 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_5()
2354 …"OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay… in of_unittest_overlay_5()
[all …]
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/linux/arch/powerpc/include/uapi/asm/ |
| H A D | kvm_para.h | 27 * 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].
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | manager.hpp | 67 * needs to occur before the regulators have been enabled/turned on.
81 * on. It needs to occur after the regulators have been configured and
85 * off. It needs to occur before the regulators have been disabled/turned
|
| /openbmc/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()
|
| /openbmc/linux/Documentation/ABI/ |
| H A 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
|
| /openbmc/qemu/qga/ |
| H A D | commands-windows-ssh.c | 101 * errp -> Error structure to set any errors that occur.
134 * errp -> Error structure to set any errors that occur
194 * errp -> Error structure to set any errors that occur
425 * errp: Error structure that will contain any errors if they occur.
456 * errp -> Contains any errors that occur.
663 * errp -> Contains any errors that occur.
|
| /openbmc/u-boot/scripts/ |
| H A D | Makefile.extrawarn | 6 # W=1 - warnings that may be relevant and does not occur too often
7 # W=2 - warnings that occur quite often but may still be relevant
|
| /openbmc/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
|
| /openbmc/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()
|
| /openbmc/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
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-general.rst | 39 new release if changes occur that give rise to problems.
62 incompatibilities might occur when you upgrade. For example, if your
|
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/fw/ |
| H A D | file.h | 859 * 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
|
| /openbmc/docs/designs/ |
| H A D | hw-fault-monitor.md | 52 - FRU fault manager controls the blinking of LEDs when faults occur:
78 occur less frequently, while less severe errors such as correctable errors
127 interest in order to be alerted when fault events occur. The fault monitor will
|
| H A D | power-recovery.md | 19 occur. For example, some systems have op-panels, and on these op-panels there
106 reset) or in severe cases occur when there is some sort of an external outage.
184 variety of reasons an external reset can occur. Some systems are adding GPIOs to
301 Validate that when multiple black outs occur, the firmware continues to try and
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A 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
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/xorg-app/ |
| H A D | xkbevd_1.1.6.bb | 4 events and executes requested commands if they occur. "
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/ |
| H A D | Report.interface.yaml | 168 Enumerates error types that might occur during properties'
176 to 0, such conflict will occur.
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-util/ |
| H A D | makedepend_1.0.9.bb | 11 occur in these files as well."
|
| /openbmc/qemu/target/riscv/insn_trans/ |
| H A D | trans_rvi.c.inc | 975 * side effects that might occur on a csr read.
990 * side effects that might occur on a csr read.
1005 * cause any of the side effects that might occur on a csr write.
1034 * cause any of the side effects that might occur on a csr write.
1066 * side effects that might occur on a csr read.
1080 * side effects that might occur on a csr read.
1095 * cause any of the side effects that might occur on a csr write.
1123 * cause any of the side effects that might occur on a csr write.
|