Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210524111514.65713-1-dzagorui@cisco.com>
In-Reply-To: <20210524111514.65713-1-dzagorui@cisco.com>
From:   Namhyung Kim <namhyung@kernel.org>
Date:   Mon, 24 May 2021 21:34:16 -0700
Message-ID: <CAM9d7chkR-tcr1B1EePjK4otEDU7=60c1KsPZjYy_YH-=f9zUQ@mail.gmail.com>
Subject: Re: [PATCH v8 1/3] perf report: compile tips.txt in perf binary
To:     Denys Zagorui <dzagorui@cisco.com>
Cc:     Jiri Olsa <jolsa@redhat.com>,
        linux-kernel <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>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hello,

On Mon, May 24, 2021 at 4:15 AM Denys Zagorui <dzagorui@cisco.com> 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 all three patches,

Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks,
Namhyung