From: Jiri Olsa <jolsa@redhat.com>
To: "fujita.yuya@fujitsu.com" <fujita.yuya@fujitsu.com>
Cc: 'Peter Zijlstra' <peterz@infradead.org>,
'Ingo Molnar' <mingo@redhat.com>,
'Arnaldo Carvalho de Melo' <acme@kernel.org>,
'Jiri Olsa' <jolsa@kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Fix variable name's inconsistency in hists__for_each macro
Date: Thu, 19 Dec 2019 09:51:06 +0100 [thread overview]
Message-ID: <20191219085106.GA8141@krava> (raw)
In-Reply-To: <OSAPR01MB1588E1C47AC22043175DE1B2E8520@OSAPR01MB1588.jpnprd01.prod.outlook.com>
On Thu, Dec 19, 2019 at 08:08:32AM +0000, fujita.yuya@fujitsu.com wrote:
> From: Yuya Fujita <fujita.yuya@fujitsu.com>
>
> Variable names are inconsistent in hists__for_each macro.
> Due to this inconsistency, the macro replaces its second argument with "fmt"
> regardless of its original name.
> So far it works because only "fmt" is passed to the second argument.
hum, I think it works because all the instances that use these macros
have 'fmt' variable passed in
> However, this behavior is not expected and should be fixed.
>
> Fixes: f0786af536bb ("perf hists: Introduce hists__for_each_format macro")
> Fixes: aa6f50af822a ("perf hists: Introduce hists__for_each_sort_list macro")
nice ;-)
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
> Signed-off-by: Yuya Fujita <fujita.yuya@fujitsu.com>
> ---
> tools/perf/util/hist.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/hist.h b/tools/perf/util/hist.h
> index 4528690..0aa63ae 100644
> --- a/tools/perf/util/hist.h
> +++ b/tools/perf/util/hist.h
> @@ -339,10 +339,10 @@ static inline void perf_hpp__prepend_sort_field(struct perf_hpp_fmt *format)
> list_for_each_entry_safe(format, tmp, &(_list)->sorts, sort_list)
>
> #define hists__for_each_format(hists, format) \
> - perf_hpp_list__for_each_format((hists)->hpp_list, fmt)
> + perf_hpp_list__for_each_format((hists)->hpp_list, format)
>
> #define hists__for_each_sort_list(hists, format) \
> - perf_hpp_list__for_each_sort_list((hists)->hpp_list, fmt)
> + perf_hpp_list__for_each_sort_list((hists)->hpp_list, format)
>
> extern struct perf_hpp_fmt perf_hpp__format[];
>
> --
> 1.7.1
>
next prev parent reply other threads:[~2019-12-19 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 8:08 [PATCH] perf tools: Fix variable name's inconsistency in hists__for_each macro fujita.yuya
2019-12-19 8:51 ` Jiri Olsa [this message]
2019-12-19 16:54 ` 'Arnaldo Carvalho de Melo'
2019-12-19 21:45 ` 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=20191219085106.GA8141@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=fujita.yuya@fujitsu.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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).