[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cff37252-4bef-8847-7373-d09008aa475a@linux.intel.com>
Date: Thu, 7 Oct 2021 16:51:57 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: James Clark <james.clark@....com>, acme@...nel.org,
john.garry@...wei.com, linux-perf-users@...r.kernel.org
Cc: Nick.Forrington@....com, Andrew.Kilroy@....com,
Will Deacon <will@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Leo Yan <leo.yan@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] perf tools: Enable strict JSON parsing
On 10/7/2021 4:05 AM, James Clark wrote:
> After a discussion on "[PATCH 1/4] perf vendor events: Syntax corrections in Neoverse N1 json",
> John Garry suggested that we can just modify the parser to make it more strict. Hopefully this will
> remove the need to apply any future JSON comma fixup commits.
>
> Applies on top of "[PATCH v2 1/3] perf vendor events: Syntax corrections in Neoverse N1 json" on
> perf/core.
Looks good to me. The Intel files are already generated by automated
tools using the standard python JSON writer, I guess if it's out of sync
someone must have edited it by hand. So it should be fine to fix it.
Reviewed-by: Andi Kleen <ak@...ux.intel.com>
-Andi
Powered by blists - more mailing lists