All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Michael Petlan <mpetlan@redhat.com>,
	Andi Kleen <ak@linux.intel.com>, Kajol Jain <kjain@linux.ibm.com>
Subject: Re: [PATCH perf/urgent] perf expr: Fix copy/paste mistake
Date: Mon, 16 Mar 2020 10:52:28 -0300	[thread overview]
Message-ID: <20200316135228.GG9917@kernel.org> (raw)
In-Reply-To: <20200315155609.603948-1-jolsa@kernel.org>

Em Sun, Mar 15, 2020 at 04:56:09PM +0100, Jiri Olsa escreveu:
> Copy/paste leftover from recent refactor.

This has not made into perf/urgent, so I've applied it to my perf/core
branch, thanks,

[acme@quaco perf]$ git tag --contains 26226a97724d
perf-core-for-mingo-5.7-20200310
[acme@quaco perf]$

- Arnaldo
 
> Fixes: 26226a97724d ("perf expr: Move expr lexer to flex")
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
>  tools/perf/util/expr.l | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/perf/util/expr.l b/tools/perf/util/expr.l
> index 1928f2a3dddc..eaad29243c23 100644
> --- a/tools/perf/util/expr.l
> +++ b/tools/perf/util/expr.l
> @@ -79,10 +79,10 @@ symbol		{spec}*{sym}*{spec}*{sym}*
>  	{
>  		int start_token;
>  
> -		start_token = parse_events_get_extra(yyscanner);
> +		start_token = expr_get_extra(yyscanner);
>  
>  		if (start_token) {
> -			parse_events_set_extra(NULL, yyscanner);
> +			expr_set_extra(NULL, yyscanner);
>  			return start_token;
>  		}
>  	}
> -- 
> 2.24.1
> 

-- 

- Arnaldo

  reply	other threads:[~2020-03-16 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 15:56 [PATCH perf/urgent] perf expr: Fix copy/paste mistake Jiri Olsa
2020-03-16 13:52 ` Arnaldo Carvalho de Melo [this message]
2020-03-19 14:10 ` [tip: perf/core] " tip-bot2 for Jiri Olsa

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=20200316135228.GG9917@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    /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.