mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: remove unused ret
Date: Tue, 4 Feb 2020 19:11:04 +0800	[thread overview]
Message-ID: <e47edc57-b6a4-1d95-31fe-6d649c7f51f0@linux.alibaba.com> (raw)
In-Reply-To: <20200121173549.3de146d5@gandalf.local.home>



在 2020/1/22 上午6:35, Steven Rostedt 写道:
> On Tue, 21 Jan 2020 13:54:43 +0800
> Alex Shi <alex.shi@linux.alibaba.com> wrote:
> 
>> No body care the variable 'ret' in function unregister_field_var_hists,
>> better to remove it.
>>
>> Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
>> Cc: Steven Rostedt <rostedt@goodmis.org> 
>> Cc: Ingo Molnar <mingo@redhat.com> 
>> Cc: linux-kernel@vger.kernel.org 
>> ---
>>  kernel/trace/trace_events_hist.c | 3 +--
>>  1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
>> index f62de5f43e79..0acfac95ca2a 100644
>> --- a/kernel/trace/trace_events_hist.c
>> +++ b/kernel/trace/trace_events_hist.c
>> @@ -5712,12 +5712,11 @@ static void unregister_field_var_hists(struct hist_trigger_data *hist_data)
>>  	struct trace_event_file *file;
>>  	unsigned int i;
>>  	char *cmd;
>> -	int ret;
>>  
>>  	for (i = 0; i < hist_data->n_field_var_hists; i++) {
>>  		file = hist_data->field_var_hists[i]->hist_data->event_file;
>>  		cmd = hist_data->field_var_hists[i]->cmd;
>> -		ret = event_hist_trigger_func(&trigger_hist_cmd, file,
>> +		event_hist_trigger_func(&trigger_hist_cmd, file,
> 
> I pulled in some of your other patches (removing unused macros), but
> these that remove 'ret' I prefer not to take. Yes, we currently do not
> use ret here, but the compiler will easily remove its existence. I'm
> thinking if anything, we should report an error if they do return
> something other than success.
> 
> -- Steve
> 

Pretty make sense. :)

Thanks!
Alex


      reply	other threads:[~2020-02-04 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21  5:54 Alex Shi
2020-01-21 22:35 ` Steven Rostedt
2020-02-04 11:11   ` Alex Shi [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=e47edc57-b6a4-1d95-31fe-6d649c7f51f0@linux.alibaba.com \
    --to=alex.shi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®