All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Luke Mujica <lukemujica@google.com>
Cc: peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, jolsa@redhat.com,
	namhyung@kernel.org, linux-kernel@vger.kernel.org,
	irogers@google.com, eranian@google.com
Subject: Re: [PATCH] perf parse-events: Remove unused variable: error
Date: Fri, 5 Jul 2019 13:39:24 -0300	[thread overview]
Message-ID: <20190705163924.GA8600@kernel.org> (raw)
In-Reply-To: <20190703222509.109616-2-lukemujica@google.com>

Em Wed, Jul 03, 2019 at 03:25:09PM -0700, Luke Mujica escreveu:
> Remove error variable because it is declared but not used in
> parse-events.y or in the generated parse-events.c.

Thanks, applied
 
> Signed-off-by: Luke Mujica <lukemujica@google.com>
> ---
>  tools/perf/util/parse-events.y | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/tools/perf/util/parse-events.y b/tools/perf/util/parse-events.y
> index 172dbb73941f..f1c36ed1cf36 100644
> --- a/tools/perf/util/parse-events.y
> +++ b/tools/perf/util/parse-events.y
> @@ -480,7 +480,6 @@ event_bpf_file:
>  PE_BPF_OBJECT opt_event_config
>  {
>  	struct parse_events_state *parse_state = _parse_state;
> -	struct parse_events_error *error = parse_state->error;
>  	struct list_head *list;
>  
>  	ALLOC_LIST(list);
> -- 
> 2.22.0.410.gd8fdbe21b5-goog

-- 

- Arnaldo

  reply	other threads:[~2019-07-05 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 22:25 [PATCH] perf parse-events: Remove unused variable i Luke Mujica
2019-07-03 22:25 ` [PATCH] perf parse-events: Remove unused variable: error Luke Mujica
2019-07-05 16:39   ` Arnaldo Carvalho de Melo [this message]
2019-07-13 11:04   ` [tip:perf/urgent] " tip-bot for Luke Mujica
2019-07-05 16:39 ` [PATCH] perf parse-events: Remove unused variable i Arnaldo Carvalho de Melo
2019-07-13 11:03 ` [tip:perf/urgent] perf parse-events: Remove unused variable 'i' tip-bot for Luke Mujica

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=20190705163924.GA8600@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukemujica@google.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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.