On Thu, Apr 06, 2017 at 12:17:00PM +0100, Lionel Landwerlin wrote:
> On 06/04/17 12:12, Chris Wilson wrote:
> >On Thu, Apr 06, 2017 at 12:04:40PM +0100, Lionel Landwerlin wrote:
> >>This is a pretty good indicator that something's gone horribly wrong.
> >Do you run IPEHR through the decoder? That w
On 06/04/17 12:12, Chris Wilson wrote:
On Thu, Apr 06, 2017 at 12:04:40PM +0100, Lionel Landwerlin wrote:
This is a pretty good indicator that something's gone horribly wrong.
Do you run IPEHR through the decoder? That was somewhere on the todo
list for intel_error_decode.
-Chris
Not yet, I'
On Thu, Apr 06, 2017 at 12:04:40PM +0100, Lionel Landwerlin wrote:
> This is a pretty good indicator that something's gone horribly wrong.
Do you run IPEHR through the decoder? That was somewhere on the todo
list for intel_error_decode.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
This is a pretty good indicator that something's gone horribly wrong.
Signed-off-by: Lionel Landwerlin
---
src/intel/tools/aubinator_error_decode.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/intel/tools/aubinator_error_decode.c
b/src/intel/tools/aubinator_error_
