> -----Original Message-----
> From: Borislav Petkov <bp@xxxxxxx>
> Sent: Thursday, March 1, 2018 7:00 AM
> To: Ghannam, Yazen <Yazen.Ghannam@xxxxxxx>
> Cc: Tony Luck <tony.luck@xxxxxxxxx>; linux-efi@xxxxxxxxxxxxxxx; linux-
> kernel@xxxxxxxxxxxxxxx; ard.biesheuvel@xxxxxxxxxx; x86@xxxxxxxxxx
> Subject: Re: [PATCH v2 0/8] Decode IA32/X64 CPER
>
> On Wed, Feb 28, 2018 at 08:58:15PM +0000, Ghannam, Yazen wrote:
> > 1) We keep this set mostly as-is. This would be our fallback if we don't have
> > anything better.
>
> Yes, sounds good. We try to decode it as MCE and if we cannot, we dump
> the raw CPER record.
>
> > 2) I add the MCA decoding to this set. I was thinking to do this in a separate
> > set but maybe it's better to do it all together.
>
> I'm fine if you do it separately, as long as you do it so that we have
> user-friendly decoding in the end.
>
I wanted to add the MCA decoding to this set but I got caught up with something
else and haven't had time to do it.
Is it alright if I go ahead and just send the v3 of this set without the MCA decoding?
I was hoping this could be accepted in the next merge window. And if that's still
possible I'd like to have some CPER decoding sooner rather than nothing.
Thanks,
Yazen
��.n��������+%������w��{.n�����{����* jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
