From: "Arnd Bergmann" <arnd@arndb.de>
To: "James Clark" <james.clark@linaro.org>,
"Joel May" <joel-linux@jmay.us>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>, "Leo Yan" <leo.yan@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
"Linux perf Profiling" <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] arm64: perf: fix syscalltbl path base
Date: Mon, 15 Dec 2025 10:33:00 +0100 [thread overview]
Message-ID: <23c07ac4-ff13-47a5-824a-e7af1d1847a3@app.fastmail.com> (raw)
In-Reply-To: <fcefc3c0-541d-40cc-84e3-9c2460308bdb@linaro.org>
On Mon, Dec 15, 2025, at 09:47, James Clark wrote:
> On 15/12/2025 00:12, Joel May wrote:
>
> Hi Joel,
>
> There is a similar fix on the list here:
>
> https://lore.kernel.org/linux-perf-users/20251204-perf_fix_syscall_header-v1-1-b8e27f74ed6a@arm.com/
>
> I'm not sure if commit 1 alone will also fix your issue, or we'd need to
> collapse both of the commits in that set.
>
> The first commit has an older fixes: tag and also fixes some other
> issues so it might be better to take that one rather than this one.
I don't understand that other "fix", doesn't that just work around
the arm64 build issue by adding another special case for arm64?
If we want the tools directory to have a copy of the generated unistd.h
files instead of generating them, it should at the minimum be done
the same across all architectures.
Arnd
next prev parent reply other threads:[~2025-12-15 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b2651f20-6f3a-49f5-9cd8-3fb028b2cab5@app.fastmail.com>
2025-12-15 8:47 ` [PATCH] arm64: perf: fix syscalltbl path base James Clark
2025-12-15 9:33 ` Arnd Bergmann [this message]
2025-12-15 10:52 ` James Clark
2025-12-15 11:28 ` Leo Yan
2025-12-15 12:22 ` Arnd Bergmann
2025-12-15 16:49 ` Leo Yan
2025-12-16 7:17 ` Arnd Bergmann
2025-12-16 12:04 ` Leo Yan
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=23c07ac4-ff13-47a5-824a-e7af1d1847a3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=james.clark@linaro.org \
--cc=joel-linux@jmay.us \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=will@kernel.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).