[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <172730392642.3246951.14949475927195901266.b4-ty@kernel.org>
Date: Wed, 25 Sep 2024 15:41:25 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Masum Reza <masumrezarock100@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
"Liang, Kan" <kan.liang@...ux.intel.com>,
Ze Gao <zegao2021@...il.com>,
Yang Jihong <yangjihong1@...wei.com>,
Yunseong Kim <yskelg@...il.com>,
linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf evsel: display dmesg command of showing a hardcoded path
On Sun, 22 Sep 2024 16:56:16 +0530, Masum Reza wrote:
> In non-FHS compliant distros like NixOS, nothing resides in `/bin`
> and `/usr/bin`. Instead dynamically symlinked into
> `/run/current-system/sw/bin/`, the executable resides in `/nix/store`.
>
> With this patch,`/bin` prefix from the dmesg command in the error
> message is stripped.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists