From: Heiko Stuebner <heiko@sntech•de>
To: heiko@sntech•de
Cc: rosenp@gmail•com, linux-arm-kernel@lists•infradead.org,
linux-rockchip@lists•infradead.org, linux-clk@vger•kernel.org,
kernel test robot <lkp@intel•com>
Subject: [PATCH] clk: rockchip: don't COMPILE_TEST builds on M68K
Date: Wed, 3 Jun 2026 23:37:26 +0200 [thread overview]
Message-ID: <20260603213726.1025094-1-heiko@sntech.de> (raw)
Rockchip clock drivers use hash-tables with enums as inputs.
M68K does interesting things in its __hash_32() implementation, casting
that u32 input to an u16 and therefore triggering warnings like:
drivers/clk/rockchip/clk-rk3528.c: note: in included file (through include/linux/hash.h, include/linux/slab.h):
arch/m68k/include/asm/hash.h:57:24: sparse: sparse: cast truncates bits from constant value (18720 becomes 8720)
arch/m68k/include/asm/hash.h:57:24: sparse: sparse: cast truncates bits from constant value (1e8e8 becomes e8e8)
As M68K should never ever need Rockchip clock drivers, simply disable
compile-tests for M68K.
Fixes: 7edfb7fb58ee ("clk: rockchip: allow COMPILE_TEST builds")
Reported-by: kernel test robot <lkp@intel•com>
Closes: https://lore.kernel.org/oe-kbuild-all/202605191434.PQkj2Rki-lkp@intel.com/
Signed-off-by: Heiko Stuebner <heiko@sntech•de>
---
drivers/clk/rockchip/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/rockchip/Kconfig b/drivers/clk/rockchip/Kconfig
index 85133498f013..8b49fe6f46fb 100644
--- a/drivers/clk/rockchip/Kconfig
+++ b/drivers/clk/rockchip/Kconfig
@@ -4,6 +4,7 @@
config COMMON_CLK_ROCKCHIP
bool "Rockchip clock controller common support"
depends on ARCH_ROCKCHIP || COMPILE_TEST
+ depends on !M68K
default ARCH_ROCKCHIP
help
Say y here to enable common clock controller for Rockchip platforms.
--
2.47.3
next reply other threads:[~2026-06-03 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 21:37 Heiko Stuebner [this message]
2026-06-04 7:56 ` [PATCH] clk: rockchip: don't COMPILE_TEST builds on M68K Geert Uytterhoeven
2026-06-04 8:59 ` Heiko Stuebner
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=20260603213726.1025094-1-heiko@sntech.de \
--to=heiko@sntech$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-clk@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
--cc=lkp@intel$(echo .)com \
--cc=rosenp@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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