On 16 July 2018 at 12:04, Andy Shevchenko <[email protected]> wrote: > The commit > > 2f74f09bce4f ("efi: parse ARM processor error") > > brought inconsistency in UUID types which are used across the CPER. > > Fix this by moving to use guid_t API everywhere. > > Cc: Tyler Baicar <[email protected]> > Signed-off-by: Andy Shevchenko <[email protected]> > --- > drivers/firmware/efi/cper.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/firmware/efi/cper.c b/drivers/firmware/efi/cper.c > index 3bf0dca378a6..68f332dd227c 100644 > --- a/drivers/firmware/efi/cper.c > +++ b/drivers/firmware/efi/cper.c > @@ -459,7 +459,7 @@ cper_estatus_print_section(const char *pfx, struct > acpi_hest_generic_data *gdata > else > goto err_section_too_small; > #if defined(CONFIG_ARM64) || defined(CONFIG_ARM) > - } else if (!uuid_le_cmp(*sec_type, CPER_SEC_PROC_ARM)) { > + } else if (guid_equal(sec_type, &CPER_SEC_PROC_ARM)) { > struct cper_sec_proc_arm *arm_err = > acpi_hest_get_payload(gdata); > > printk("%ssection_type: ARM processor error\n", newpfx);
Thanks, I'll queue this in efi/next -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
