Lines Matching full:errors

14 - [Boot Fail on Hardware Errors](#boot-fail-on-hardware-errors)
106 Any errors passed into these APIs must be known to phosphor-logging, usually by
107 being defined in `<phosphor-logging/elog-errors.hpp>`. The errors must also be
109 for details on how get errors into these headers.
114 #include <phosphor-logging/elog-errors.hpp>
152 #include <phosphor-logging/elog-errors.hpp>
181 `<error-category>.errors.yaml` file, and define any metadata in the
183 repository. During the build, phosphor-logging generates the elog-errors.hpp
191 `xyz/openbmc_project/Control/Device.errors.yaml`, the errors that come from that
194 In rare cases, one may want one to define their errors in the same repository
206       an elog-errors.hpp file that just contains the local errors, and check
207       that into the repository and include it where the errors are needed.
235 Unlike the previous APIs where errors could also act as exceptions that could be
244 `Timeout` error in `xyz/openbmc_project/Common.errors.yaml` will have a Message
253 2. If creating a new error, use the same naming scheme as other errors, which
275 …/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Software/Version.errors.yaml
463 ## Boot Fail on Hardware Errors