mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Emmanouil Maroudas <emmanouil.maroudas@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 0/2] perf tools: minor fixes regarding macro usage
Date: Fri, 3 Jul 2020 12:55:09 +0200	[thread overview]
Message-ID: <20200703105509.GB3261456@krava> (raw)
In-Reply-To: <20200628232521.22686-1-emmanouil.maroudas@gmail.com>

On Mon, Jun 29, 2020 at 02:25:19AM +0300, Emmanouil Maroudas wrote:
>     Hello,
> 
>     Here are some minor fixes for perf tools regarding *SEC_PER*SEC macro usage,
>     found while reading the code.
> 
>     Patch 1 replaces a macro with a more suitable one (same value, different name).
>     Patch 2 converts some hardcoded values (which seem appropriate IMHO) with their
>     respective macros.
> 
>     Based on v5.8-rc3.
> 
>     No functionality change. The final perf binary is the same, before and after
>     these patches.
> 
>     Thanks,
>     Emmanouil Maroudas
> 
> Emmanouil Maroudas (2):
>   perf stat: use proper macro for time conversions
>   perf tools: use *SEC_PER_*SEC macros

Acked-by: Jiri Olsa <jolsa@redhat.com>

thanks,
jirka

> 
>  tools/perf/builtin-record.c |  2 +-
>  tools/perf/builtin-stat.c   | 12 ++++++------
>  tools/perf/builtin-trace.c  |  2 +-
>  3 files changed, 8 insertions(+), 8 deletions(-)
> 
> -- 
> 2.17.1
> 


      parent reply	other threads:[~2020-07-03 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 23:25 Emmanouil Maroudas
2020-06-28 23:25 ` [PATCH 1/2] perf stat: use proper macro for time conversions Emmanouil Maroudas
2020-06-28 23:25 ` [PATCH 2/2] perf tools: use *SEC_PER_*SEC macros Emmanouil Maroudas
2020-07-03 10:55 ` Jiri Olsa [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=20200703105509.GB3261456@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=emmanouil.maroudas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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 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®