/openbmc/linux/drivers/mmc/host/ |
H A D | cb710-mmc.c | 112 static int cb710_check_event(struct cb710_slot *slot, u8 what) in cb710_check_event() argument 137 if ((status >> 8) & what) { in cb710_check_event() 138 cb710_write_port_8(slot, CB710_MMC_STATUS1_PORT, what); in cb710_check_event() 145 static int cb710_wait_for_event(struct cb710_slot *slot, u8 what) in cb710_wait_for_event() argument 155 while (!(err = cb710_check_event(slot, what))) { in cb710_wait_for_event() 172 limit, what, e, x); in cb710_wait_for_event()
|
/openbmc/openbmc/poky/meta/recipes-devtools/qemu/qemu/ |
H A D | 0002-apic-fixup-fallthrough-to-PIC.patch | 9 APIC is disabled it doesn't matter what the local APIC config says. 12 guest will receive a general protection fault, similar to what is seen
|
/openbmc/openpower-hw-diags/analyzer/ |
H A D | analyzer_main.cpp | 139 trace::err(e.what()); in analyzeHardware() 180 trace::err(e.what()); in analyzeHardware()
|
/openbmc/phosphor-pid-control/ |
H A D | main.cpp | 152 std::cerr << "Failed during building: " << e.what() << "\n"; in restartControlLoops() 210 << e.what() << "\n"; in tryRestartControlLoops() 250 << e.what() << "\n"; in tryTerminateControlLoops()
|
/openbmc/linux/tools/testing/selftests/net/mptcp/ |
H A D | mptcp_inq.c | 545 static int rcheck(int wstatus, const char *what) in rcheck() argument 550 fprintf(stderr, "%s exited, status=%d\n", what, WEXITSTATUS(wstatus)); in rcheck() 553 xerror("%s killed by signal %d\n", what, WTERMSIG(wstatus)); in rcheck() 555 xerror("%s stopped by signal %d\n", what, WSTOPSIG(wstatus)); in rcheck()
|
/openbmc/openpower-occ-control/ |
H A D | occ_status.cpp | 51 "INST", instance, "ERROR", e.what()); in occActive() 128 "INST", instance, "ERROR", e.what()); in occActive() 396 "PATH", prefixPath, "ERROR", e.what()); in getHwmonPath() 699 "PATH", path, "ERROR", e.what()); in readProcAssociation()
|
H A D | powercap.cpp | 220 "ERR", e.what()); in updatePcapBounds() 252 "PATH", PCAP_PATH, "ERR", e.what()); in getPcap() 271 "PATH", PCAP_PATH, "ERR", e.what()); in getPcapEnabled()
|
/openbmc/phosphor-logging/extensions/openpower-pels/ |
H A D | device_callouts.cpp | 301 " " + addrString + ": " + std::string{e.what()}; in calloutI2C() 349 std::string{e.what()}; in calloutFSI() 395 " " + busString + " " + addrString + ": " + e.what(); in calloutFSII2C() 434 " " + busString + ": " + std::string{e.what()}; in calloutFSISPI()
|
/openbmc/linux/Documentation/process/ |
H A D | howto.rst | 52 been created over time based on what they have found to work best for 93 what is necessary to do to configure and build the kernel. People 155 happen, and what to do if you want to get a change into one of these 160 development. Please consult this list if you do not find what you 164 A good introduction describing exactly what a patch is and how to 216 and possibly be pointed in the direction of what to go work on next, if 272 It is worth mentioning what Andrew Morton wrote on the linux-kernel 299 in the kernel tree documents what kinds of changes are acceptable for 307 development in source repositories. That way, others can see what is 337 This way, the linux-next gives a summary outlook onto what will be [all …]
|
/openbmc/linux/arch/x86/kernel/ |
H A D | verify_cpu.S | 100 movl $0x1,%eax # Does the cpu have what it takes 111 movl $0x80000001,%eax # Does the cpu have what it takes
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/open-vm-tools/open-vm-tools/ |
H A D | 0004-Use-configure-to-test-for-feature-instead-of-platfor.patch | 6 Test for various functions instead of trying to keep track of what 7 platform and what version of the given platform has support for what.
|
/openbmc/phosphor-power/tools/power-utils/ |
H A D | updater.cpp | 172 lg2::error("Error reading firmware: {ERROR}", "ERROR", e.what()); in readFirmwareBytes() 223 "PATH", devPath, "ERR", e.what()); in Updater() 346 lg2::error("{EX}", "EX", ex.what()); in isReadyToUpdate()
|
/openbmc/linux/drivers/thunderbolt/ |
H A D | Kconfig | 27 Only enable this if you know what you are doing! Never enable 52 cable back to the host. Only enable this if you know what you
|
/openbmc/phosphor-logging/tools/phosphor-logging/templates/ |
H A D | elog-gen-template.mako.hpp | 1 ## Note that this file is not auto generated, it is what generates the 137 const char* what() const noexcept override
|
/openbmc/linux/drivers/vfio/pci/ |
H A D | Kconfig | 25 If you don't know what to do here, say N. 36 If you don't know what to do here, say N.
|
/openbmc/phosphor-power/phosphor-regulators/test/actions/ |
H A D | compare_vpd_action_tests.cpp | 161 EXPECT_STREQ(e.what(), in TEST() 173 EXPECT_STREQ(re.what(), "D-Bus error: Invalid object path"); in TEST()
|
H A D | action_environment_tests.cpp | 181 EXPECT_STREQ(ia_error.what(), in TEST() 248 EXPECT_STREQ(ia_error.what(), in TEST() 320 EXPECT_STREQ(r_error.what(), in TEST()
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | diffmark | 1 1. you can do what you want with it
|
/openbmc/linux/drivers/hwmon/ |
H A D | asus_atk0110.c | 400 char const *what; in atk_sensor_type() local 404 what = "voltage"; in atk_sensor_type() 407 what = "temperature"; in atk_sensor_type() 410 what = "fan"; in atk_sensor_type() 413 what = "unknown"; in atk_sensor_type() 417 return what; in atk_sensor_type() 430 char const *what; in atk_print_sensor() local 438 what = atk_sensor_type(flags); in atk_print_sensor() 440 dev_dbg(dev, "%s: %#llx %s [%llu-%llu] %s\n", what, in atk_print_sensor()
|
/openbmc/phosphor-ipmi-flash/ |
H A D | bmc_json_config.md | 13 Let's break them down, what they contain and what it means, and then how to 74 The `type` field expects a string and will control what other parameters are 87 the BMC for updating various firmware, it needs to be told what to do to verify 99 similarly to the `handler` field. This dictates what other parameters may be 209 Action types are used to define what to do for a specific requested action, such
|
/openbmc/openpower-proc-control/extensions/phal/ |
H A D | phal_error.cpp | 125 pdbg_target_path(target), e.what()) in pdbgCallbackToGetTgtReqAttrsVal() 319 pdbg_target_path(procTarget), e.what()) in processNonFunctionalBootProc() 826 std::format("processPlatBootError: exception({})", ex.what()) in processPlatBootError() 858 std::format("processBootError: exception({})", ex.what()).c_str()); in processBootError() 919 std::format("captureFFDC: Exception({})", phalError.what()) in processSbeBootError() 1002 entry("EXCEPTION=%s", e.what())); in getLogLevelFromEnv()
|
/openbmc/google-ipmi-sys/ |
H A D | handler.cpp | 410 entry("WHAT=%s", ex.what())); in hostPowerOffDelay() 499 entry("WHAT=%s", ex.what())); in accelOobDeviceCount() 522 entry("WHAT=%s", ex.what())); in accelOobDeviceName() 565 entry("WHAT=%s", ex.what()), in accelOobRead() 655 entry("WHAT=%s", ex.what()), in accelOobWrite() 700 entry("WHAT=%s", ex.what())); in linuxBootDone()
|
/openbmc/u-boot/doc/ |
H A D | README.log | 14 But for digging into what is happening in a particular area, or for debugging 15 a problem it is often useful to see what U-Boot is doing in more detail than 169 Filters are attached to log drivers to control what those drivers emit. Only 205 Code size impact depends largely on what is enabled. The following numbers are 242 Figure out what to do with BUG(), BUG_ON() and warn_non_spl() 244 Figure out what to do with assert()
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | log-writes.rst | 19 the log in a way that correlates to what is on disk and not what is in cache, 35 Again this is to simulate what is actually on disk, this allows us to detect 52 which isn't quite what happened and wouldn't be caught during the log replay.
|
/openbmc/linux/Documentation/livepatch/ |
H A D | cumulative-patches.rst | 41 the transition to has finished. It helps to clearly see what code is 87 easier in many others. Only the new cumulative livepatch knows what 88 fixes/features are added/removed and what special actions are necessary
|