Re: [PATCH] ppc/spapr: Set the effective address provided flag in mc error log.

2020-03-17 Thread Mahesh J Salgaonkar
t; > > This series seems to have some coding style problems. See output below for > > more information: > > > > Subject: [PATCH] ppc/spapr: Set the effective address provided flag in mc > > error log. > > Message-id: 158444819283.31599.12155058652686614304.st

Re: [PATCH] ppc/spapr: Set the effective address provided flag in mc error log.

2020-03-17 Thread Greg Kurz
e information: > > Subject: [PATCH] ppc/spapr: Set the effective address provided flag in mc > error log. > Message-id: 158444819283.31599.12155058652686614304.stgit@jupiter > Type: series > > === TEST SCRIPT BEGIN === > #!/bin/bash > git rev-parse base > /dev/nul

Re: [PATCH] ppc/spapr: Set the effective address provided flag in mc error log.

2020-03-17 Thread no-reply
Patchew URL: https://patchew.org/QEMU/158444819283.31599.12155058652686614304.stgit@jupiter/ Hi, This series seems to have some coding style problems. See output below for more information: Subject: [PATCH] ppc/spapr: Set the effective address provided flag in mc error log. Message-id

[PATCH] ppc/spapr: Set the effective address provided flag in mc error log.

2020-03-17 Thread Mahesh Salgaonkar
Per PAPR, it is expected to set effective address provided flag in sub_err_type member of mc extended error log (i.e rtas_event_log_v6_mc.sub_err_type). This somehow got missed in original fwnmi-mce patch series. Hence guest fails to extract effective address from mce rtas log. This patch fixes tha