linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: cgel.zte@gmail.com
Cc: mingo@redhat.com, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@redhat.com,
	namhyung@kernel.org, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Minghao Chi <chi.minghao@zte.com.cn>,
	Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] tools/perf: remove redundant err variable
Date: Sat, 22 Jan 2022 17:26:34 -0300	[thread overview]
Message-ID: <Yexoer05bRAb9G/o@kernel.org> (raw)
In-Reply-To: <20220112080109.666800-1-chi.minghao@zte.com.cn>

Em Wed, Jan 12, 2022 at 08:01:09AM +0000, cgel.zte@gmail.com escreveu:
> From: Minghao Chi <chi.minghao@zte.com.cn>
> 
> Return value from perf_event__process_tracing_data() directly instead
> of taking this in another redundant variable.

Thanks, applied.

- Arnaldo

 
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
> ---
>  tools/perf/builtin-inject.c | 5 +----
>  1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/tools/perf/builtin-inject.c b/tools/perf/builtin-inject.c
> index 409b721666cb..fbf43a454cba 100644
> --- a/tools/perf/builtin-inject.c
> +++ b/tools/perf/builtin-inject.c
> @@ -535,12 +535,9 @@ static int perf_event__repipe_exit(struct perf_tool *tool,
>  static int perf_event__repipe_tracing_data(struct perf_session *session,
>  					   union perf_event *event)
>  {
> -	int err;
> -
>  	perf_event__repipe_synth(session->tool, event);
> -	err = perf_event__process_tracing_data(session, event);
>  
> -	return err;
> +	return perf_event__process_tracing_data(session, event);
>  }
>  
>  static int dso__read_build_id(struct dso *dso)
> -- 
> 2.25.1

-- 

- Arnaldo

      reply	other threads:[~2022-01-22 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  8:01 [PATCH] tools/perf: remove redundant err variable cgel.zte
2022-01-22 20:26 ` Arnaldo Carvalho de Melo [this message]

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=Yexoer05bRAb9G/o@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=cgel.zte@gmail.com \
    --cc=chi.minghao@zte.com.cn \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=zealci@zte.com.cn \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).