[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191017172823.15f242eb@gandalf.local.home>
Date: Thu, 17 Oct 2019 17:28:23 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-trace-devel@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>, Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Tzvetomir Stoyanov <tstoyanov@...are.com>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH 1/2] perf: Iterate on tep event arrays directly
On Thu, 17 Oct 2019 18:24:31 -0300
Arnaldo Carvalho de Melo <arnaldo.melo@...il.com> wrote:
> I'll add a:
>
> Fixes: bb3dd7e7c4d5 ("tools lib traceevent, perf tools: Move struct tep_handler definition in a local header file")
> Cc: stable@...r.kernel.org : v4.20+
>
> As this is when this problem starts causing the segfault when generating
> python scripts from perf.data files with multiple tracepoint events, ok?
Sure, go ahead. I realized I forgot to add a Fixes tag when sending it.
-- Steve
Powered by blists - more mailing lists