From: Jon Hunter <jonathanh@nvidia.com>
To: James Clark <james.clark@linaro.org>,
Namhyung Kim <namhyung@kernel.org>,
Arnd Bergmann <arnd@linaro.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, linux-arch@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 05/10] tools headers: Update the syscall table with the kernel sources
Date: Thu, 24 Apr 2025 08:33:20 +0100 [thread overview]
Message-ID: <96d56e78-68db-4294-ab97-423edc9c06d8@nvidia.com> (raw)
In-Reply-To: <b2a5cfc4-190f-4983-8d5e-3483a02be980@linaro.org>
On 23/04/2025 15:57, James Clark wrote:
...
>> FWIW I am seeing this build issue too on ARM64 and these changes have
>> now landed in the mainline :-(
>>
>> So would be great to get this fixed or reverted.
>>
>> Jon
>>
>
> Hi Jon,
>
> I probably should have updated this thread, but the fix is here:
>
> https://lore.kernel.org/linux-perf-users/20250417-james-perf-fix-gen-
> syscall-v1-1-1d268c923901@linaro.org/
Great!
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Thanks for fixing and sharing!
Jon
--
nvpublic
prev parent reply other threads:[~2025-04-24 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250410001125.391820-1-namhyung@kernel.org>
[not found] ` <20250410001125.391820-6-namhyung@kernel.org>
[not found] ` <f950fe96-34d3-4631-b04d-4a1584f4c2f1@linaro.org>
[not found] ` <95c9bd53-ccef-4a34-b6d2-7203df84db01@linaro.org>
2025-04-23 9:24 ` [PATCH 05/10] tools headers: Update the syscall table with the kernel sources Jon Hunter
2025-04-23 14:57 ` James Clark
2025-04-24 7:33 ` Jon Hunter [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=96d56e78-68db-4294-ab97-423edc9c06d8@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=arnd@linaro.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mingo@kernel.org \
--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