Home
last modified time | relevance | path

Searched full:proceed (Results 1 – 25 of 137) sorted by relevance

123456

/openbmc/openpower-proc-control/procedures/phal/
H A Dproc_pre_poweroff.cpp27 // Dont throw exception on failure because, we need to proceed in prePoweroff()
40 // Dont throw exception on failure because, we need to proceed in prePoweroff()
H A Dthread_stopall.cpp126 // Dont throw exception on failure because, need to proceed in threadStopAll()
/openbmc/bmcweb/redfish-core/include/registries/
H A Dupdate_message_registry.hpp94 …"Indicates that the resource or device is waiting for an action to proceed with activating an imag…
95 "Awaiting for an action to proceed with activating image '%1' on '%2'.",
107 …"Indicates that the resource or device is waiting for an action to proceed with installing an imag…
108 "Awaiting for an action to proceed with installing image '%1' on '%2'.",
/openbmc/openbmc/meta-security/dynamic-layers/meta-python/recipes-devtools/python/python3-pyinotify/
H A D0001-Make-asyncore-support-optional-for-Python-3.patch63 - When asyncore tells us we can read from the fd, we proceed processing
76 + When asyncore tells us we can read from the fd, we proceed processing
/openbmc/bmcweb/docs/
H A DOEM_SCHEMAS.md64 3. If DMTF is interested in the proposal, proceed using their documented process
70 to OpenBMC", proceed to write an OpenBMC design document about the new
/openbmc/openbmc/meta-security/meta-integrity/recipes-core/initrdscripts/
H A Dinitramfs-framework-ima.bb17 # Force proceed IMA procedure even 'no_ima' boot parameter is available.
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/
H A DEntry.interface.yaml48 A user attempted to isolate hardware to proceed with the host to
/openbmc/openbmc/poky/meta/recipes-devtools/perl-cross/files/
H A DREADME.md14 # Proceed as usual with most autoconfed packages
/openbmc/phosphor-net-ipmid/command/
H A Dsol_cmds.hpp57 * to proceed with SOL, therefore the remote console does not need to respond
/openbmc/u-boot/board/phytec/phycore_rk3288/
H A Dphycore-rk3288.c64 /* Proceed anyway, since there is no fallback option */ in rk_board_late_init()
/openbmc/qemu/include/qemu/
H A Dhbitmap.h296 * @count: Number of bits to proceed. If @start+@count > bitmap size, the whole
308 * @count: Number of bits to proceed. If @start+@count > bitmap size, the whole
336 * @count: Number of bits to proceed
/openbmc/qemu/include/exec/
H A Dreplay-core.h59 * Does not proceed to the next event in the log.
/openbmc/openbmc/meta-security/meta-integrity/recipes-core/initrdscripts/initramfs-framework-ima/
H A Dima25 fatal "No /sys/kernel/security/ima. Cannot proceed without IMA enabled in the kernel."
/openbmc/qemu/docs/devel/
H A Dcode-of-conduct.rst54 information about how to proceed.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/lmbench/lmbench/
H A Dfix-lmbench-memory-check-failure.patch4 Subject: [PATCH] lmbench: Can't proceed on some targets
6 lmbench can't proceed on some targets. The memory check fails because the
/openbmc/openbmc/poky/meta/recipes-extended/sysklogd/sysklogd/
H A Dsysklogd32 # Only proceed if /dev/xconsole is used at all
/openbmc/qemu/qapi/
H A Dreplay.json106 # Automatically proceed to the instruction count @icount, when
/openbmc/openbmc/poky/meta/recipes-core/newlib/libgloss/
H A Dfix-rs6000-crt0.patch5 do_install, we simply modify the name of the objects so the installation can proceed
/openbmc/openbmc/poky/meta/recipes-core/initscripts/initscripts-1.0/
H A Dcheckroot.sh115 # errors were corrected but that the boot may proceed.
/openbmc/openbmc/meta-ibm/meta-system1/recipes-phosphor/flash/phosphor-software-manager/
H A Dbios-update.sh5 # Check if PCH is on standby to proceed with the
/openbmc/qemu/hw/display/
H A Dsii9022.c6 * so the emulated host can proceed to read out EDID data. All subsequent
/openbmc/openbmc/poky/meta/lib/oeqa/manual/
H A Dbsp-hw.json25 "action": "proceed through default install process",
409 "action": "Proceed through default install process.",
451 "action": "Proceed through default install process.",
/openbmc/u-boot/arch/mips/lib/
H A Dcache_init.S114 * then we proceed knowing there's no L2 cache.
295 * CONFIG_SYS_MIPS_CACHE_INIT_RAM_LOAD is set then we'll proceed to
/openbmc/openbmc/poky/meta/files/
H A Dtoolchain-shar-extract.sh205 printf "If you continue, existing files will be overwritten! Proceed [y/N]? "
209 printf "You are about to install the SDK to \"$target_sdk_dir\". Proceed [Y/n]? "
/openbmc/docs/designs/
H A Ddesign-template.md41 ASCII diagrams. Plain text will allow the review to proceed without having to

123456