All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jin Yao <yao.jin@linux.intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] perf tools: Fix hybrid config terms list corruption
Date: Sat, 11 Sep 2021 12:57:14 +0200	[thread overview]
Message-ID: <YTyLipYOF8cSB/YC@krava> (raw)
In-Reply-To: <20210909125508.28693-1-adrian.hunter@intel.com>

On Thu, Sep 09, 2021 at 03:55:06PM +0300, Adrian Hunter wrote:
> Hi
> 
> Here is a fix for an issue using perf on ADL.
> 
> 
> Adrian Hunter (2):
>       perf tools: Factor out copy_config_terms() and free_config_terms()
>       perf tools: Fix hybrid config terms list corruption

Acked-by: Jiri Olsa <jolsa@redhat.com>

thanks,
jirka

> 
>  tools/perf/util/evsel.c               | 20 +++++++++++++++-----
>  tools/perf/util/evsel.h               |  3 +++
>  tools/perf/util/parse-events-hybrid.c | 18 +++++++++++++++---
>  tools/perf/util/parse-events.c        | 27 +++++++++++++--------------
>  4 files changed, 46 insertions(+), 22 deletions(-)
> 
> 
> Regards
> Adrian
> 


  parent reply	other threads:[~2021-09-11 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 12:55 [PATCH 0/2] perf tools: Fix hybrid config terms list corruption Adrian Hunter
2021-09-09 12:55 ` [PATCH 1/2] perf tools: Factor out copy_config_terms() and free_config_terms() Adrian Hunter
2021-09-09 12:55 ` [PATCH 2/2] perf tools: Fix hybrid config terms list corruption Adrian Hunter
2021-09-10 19:32   ` Jiri Olsa
2021-09-11  6:23     ` Adrian Hunter
2021-09-11 10:57 ` Jiri Olsa [this message]
2021-09-11 19:01   ` [PATCH 0/2] " Arnaldo Carvalho de Melo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YTyLipYOF8cSB/YC@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yao.jin@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.