From: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
To: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>, Brian Cain <bcain@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-hexagon@vger.kernel.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: [PATCH 2/5] hexagon: Drop invalid UAPI header asm/signal.h
Date: Tue, 23 Dec 2025 08:04:09 +0100 [thread overview]
Message-ID: <20251223-uapi-nostdinc-v1-2-d91545d794f7@linutronix.de> (raw)
In-Reply-To: <20251223-uapi-nostdinc-v1-0-d91545d794f7@linutronix.de>
This UAPI header contains declarations of internal kernel symbols.
Such declarations are invalid. Normally headers_check.pl would report
an error, but apparently its dependency on CC_CAN_LINK prevent its
execution on hexagon so far.
As the header does not expose any additional UAPI, just make it a
regular internal kernel header. asm-generic/signal.h will be used
for the UAPI automatically, the same as before.
Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
---
arch/hexagon/include/{uapi => }/asm/signal.h | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/arch/hexagon/include/uapi/asm/signal.h b/arch/hexagon/include/asm/signal.h
similarity index 100%
rename from arch/hexagon/include/uapi/asm/signal.h
rename to arch/hexagon/include/asm/signal.h
--
2.52.0
next prev parent reply other threads:[~2025-12-23 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 7:04 [PATCH 0/5] kbuild: uapi: improvements to header testing Thomas Weißschuh
2025-12-23 7:04 ` [PATCH 1/5] kbuild: uapi: validate that headers do not use libc Thomas Weißschuh
2025-12-23 7:04 ` Thomas Weißschuh [this message]
2025-12-23 7:04 ` [PATCH 3/5] kbuild: uapi: don't compile test bpf_perf_event.h on xtensa Thomas Weißschuh
2025-12-23 7:04 ` [PATCH 4/5] kbuild: uapi: split out command conditions into variables Thomas Weißschuh
2025-12-23 7:04 ` [PATCH 5/5] kbuild: uapi: drop dependency on CC_CAN_LINK Thomas Weißschuh
2025-12-30 20:31 ` [PATCH 0/5] kbuild: uapi: improvements to header testing Nathan Chancellor
2026-01-06 22:10 ` Nathan Chancellor
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=20251223-uapi-nostdinc-v1-2-d91545d794f7@linutronix.de \
--to=thomas.weissschuh@linutronix.de \
--cc=bcain@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@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
all inboxes | Powered by JetHome®