/openbmc/linux/drivers/usb/usbip/ |
H A D | usbip_event.c | 177 int happened = 0; in usbip_event_happened() local 182 happened = 1; in usbip_event_happened() 185 return happened; in usbip_event_happened()
|
/openbmc/qemu/docs/specs/ |
H A D | pvpanic.rst | 27 a guest panic has happened and should be processed by the host 29 a guest panic has happened and will be handled by the guest; 33 a regular guest shutdown has happened and should be processed by the host
|
/openbmc/openbmc/meta-fii/meta-kudo/recipes-phosphor/watchdog/phosphor-watchdog/ |
H A D | phosphor-watchdog-host-cycle.service | 7 ExecStart=echo "Watchdog PowerCycle Action happened (no ops)"
|
H A D | phosphor-watchdog-host-poweroff.service | 7 ExecStart=echo "Watchdog PowerOff Action happened (no ops)"
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-trafaret-config_2.0.2.bb | 1 …checks config using trafaret while keeping track of actual lines of file where error has happened."
|
/openbmc/docs/designs/ |
H A D | nvmemi-over-smbus.md | 121 | TemperatureFault | bool | If warning type about temperature happened | 122 | BackupdrivesFault | bool | If warning type about backup drives happened | 123 | CapacityFault | bool | If warning type about capacity happened | 124 | DegradesFault | bool | If warning type about degrades happened | 125 | MediaFault | bool | If warning type about media happened |
|
/openbmc/linux/arch/powerpc/kernel/ |
H A D | irq_64.c | 244 : happened); in arch_local_irq_restore() 257 happened: in arch_local_irq_restore()
|
/openbmc/linux/Documentation/tools/rv/ |
H A D | common_ikm.rst | 11 When tracing (**-t**), also print the events that happened during the **rv**
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/uw-imap/uw-imap/ |
H A D | imap-2007f-format-security.patch | 15 mm_log (tmp,WARN); /* give the user a warning of what happened */
|
/openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
H A D | bug_report.md | 17 A clear and concise description of what unexpectedly happened.
|
/openbmc/linux/arch/arm/kernel/ |
H A D | hyp-stub.S | 48 strne \reg1, [\reg2] @ record what happened and give up
|
/openbmc/linux/Documentation/networking/ |
H A D | xfrm_sync.rst | 168 the change happened as a result of an update. 175 happened) is set to inform the user what happened.
|
/openbmc/openbmc/poky/meta/recipes-multimedia/libomxil/libomxil-0.9.3/ |
H A D | configure-fix.patch | 3 For example, at least the following errors happened to some compilers:
|
/openbmc/linux/Documentation/devicetree/bindings/iio/proximity/ |
H A D | semtech,sx9360.yaml | 26 and data is available or that a close/far proximity event has happened.
|
H A D | semtech,sx9310.yaml | 34 available or that a close/far proximity event has happened.
|
/openbmc/linux/Documentation/leds/ |
H A D | ledtrig-oneshot.rst | 8 happened, then the trigger turns the LED on and then keeps it off for a
|
/openbmc/bmcweb/.github/ISSUE_TEMPLATE/ |
H A D | bug_report.yml | 34 happen, and what actually happened. The more details, the better!
|
/openbmc/linux/Documentation/arch/parisc/ |
H A D | debugging.rst | 43 where exactly it happened. If you're lucky the IAOQ will point to the
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | log-writes.rst | 11 exactly as it happened originally. 52 which isn't quite what happened and wouldn't be caught during the log replay.
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | persist.rst | 22 has no way to know what has actually happened. Perhaps the same 60 has happened; look for lines saying "root hub lost power or was reset". 157 happened and will continue to use the partition tables, inodes, and
|
/openbmc/linux/Documentation/filesystems/ext4/ |
H A D | super.rst | 363 - First time an error happened, in seconds since the epoch. 375 - Name of function where the error happened. 379 - Line number where error happened. 391 - Line number where most recent error happened. 399 - Name of function where the most recent error happened.
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | bug-bisect.rst | 56 depending if the bug happened on the changeset you're testing
|
/openbmc/openbmc/poky/meta/recipes-devtools/automake/automake/ |
H A D | performance.patch | 46 - # happened. Such a system could not be considered "sane".
|
/openbmc/webui-vue/ |
H A D | README.md | 6 ## Hold on... What happened to phosphor-webui?
|
/openbmc/openbmc/poky/meta/recipes-extended/cpio/ |
H A D | cpio_2.15.bb | 58 # change permission after that has happened so the ptest user can write a
|