History log of /openbmc/phosphor-logging/extensions/openpower-pels/pel_rules.cpp (Results 1 – 2 of 2)
Revision Date Author Comments
# 1369ad0d 03-May-2023 Matt Spinler <spinler@us.ibm.com>

PEL: Remove old TODO comment

As usual a TODO didn't need to be done, so remove it.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ifdcf2d8a5ae4c36652eeb60bb9e536265ea13298


# f1e85e20 01-Nov-2019 Matt Spinler <spinler@us.ibm.com>

PEL: Validate the Action Flags field

According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
wh

PEL: Validate the Action Flags field

According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.

In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.

The rules being followed are documented in the PEL readme.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed

show more ...