linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Denys Zagorui <dzagorui@cisco.com>,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@redhat.com, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, namhyung@kernel.org
Subject: Re: [PATCH v8 1/3] perf report: compile tips.txt in perf binary
Date: Wed, 26 May 2021 09:46:44 -0300	[thread overview]
Message-ID: <YK5DNK6IfEe65kAO@kernel.org> (raw)
In-Reply-To: <YK428rtY1GsVFL4E@krava>

Em Wed, May 26, 2021 at 01:54:26PM +0200, Jiri Olsa escreveu:
> On Mon, May 24, 2021 at 04:15:12AM -0700, Denys Zagorui wrote:
> > It seems there is some need to have an ability to invoke perf from
> > build directory without installation
> > (84cfac7f05e1: perf tools: Set and pass DOCDIR to builtin-report.c)
> > DOCDIR definition contains an absolute path to kernel source directory.
> > It is build machine related info and it makes perf binary unreproducible.
> > 
> > This can be avoided by compiling tips.txt in perf directly.
> > 
> > Signed-off-by: Denys Zagorui <dzagorui@cisco.com>
> 
> for patchset
> 
> Acked-by: Jiri Olsa <jolsa@redhat.com>

Thanks, applied.

- Arnaldo


  reply	other threads:[~2021-05-26 12:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 11:15 [PATCH v8 1/3] perf report: compile tips.txt in perf binary Denys Zagorui
2021-05-24 11:15 ` [PATCH v8 2/3] perf tests: avoid storing an absolute path " Denys Zagorui
2021-05-27 16:53   ` Arnaldo Carvalho de Melo
2021-05-28 11:13     ` Denys Zagorui -X (dzagorui - GLOBALLOGIC INC at Cisco)
2021-05-28 12:48       ` Arnaldo Carvalho de Melo
2021-05-24 11:15 ` [PATCH v8 3/3] perf parse-events: add bison --file-prefix-map option Denys Zagorui
2021-05-25  4:34 ` [PATCH v8 1/3] perf report: compile tips.txt in perf binary Namhyung Kim
2021-05-26 11:54 ` Jiri Olsa
2021-05-26 12:46   ` Arnaldo Carvalho de Melo [this message]
2021-05-26 12:41 ` Arnaldo Carvalho de Melo

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=YK5DNK6IfEe65kAO@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dzagorui@cisco.com \
    --cc=jolsa@redhat.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;
as well as URLs for NNTP newsgroup(s).