From: Brian Masney <bmasney@redhat•com>
To: Rosen Penev <rosenp@gmail•com>
Cc: linux-rockchip@lists•infradead.org,
Michael Turquette <mturquette@baylibre•com>,
Stephen Boyd <sboyd@kernel•org>, Heiko Stuebner <heiko@sntech•de>,
Nathan Chancellor <nathan@kernel•org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail•com>,
Bill Wendling <morbo@google•com>,
Justin Stitt <justinstitt@google•com>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger•kernel.org>,
open list <linux-kernel@vger•kernel.org>,
"moderated list:ARM/Rockchip SoC support"
<linux-arm-kernel@lists•infradead.org>,
"open list:CLANG/LLVM BUILD SUPPORT:Keyword:b(?i:clang|llvm)b"
<llvm@lists•linux.dev>
Subject: Re: [PATCH] clk: rockchip: allow COMPILE_TEST builds
Date: Mon, 11 May 2026 10:50:14 -0400 [thread overview]
Message-ID: <agHspp1KZHZmMeOy@redhat.com> (raw)
In-Reply-To: <20260509003602.956186-1-rosenp@gmail.com>
On Fri, May 08, 2026 at 05:36:02PM -0700, Rosen Penev wrote:
> COMMON_CLK_ROCKCHIP already gates the Rockchip clock objects inside the
> Rockchip clock Makefile. Allow selecting it for COMPILE_TEST and use it
> for the parent Makefile descent instead of ARCH_ROCKCHIP.
>
> The per-SoC Rockchip clock symbols already have COMPILE_TEST dependencies,
> so this exposes the existing build coverage to other architectures without
> selecting the Rockchip platform.
>
> Tested with:
> make LLVM=1 ARCH=loongarch drivers/clk/rockchip/
>
> Assisted-by: Codex:GPT-5.5
> Signed-off-by: Rosen Penev <rosenp@gmail•com>
Reviewed-by: Brian Masney <bmasney@redhat•com>
next prev parent reply other threads:[~2026-05-11 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 0:36 [PATCH] clk: rockchip: allow COMPILE_TEST builds Rosen Penev
2026-05-11 14:50 ` Brian Masney [this message]
2026-05-13 10:37 ` 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=agHspp1KZHZmMeOy@redhat.com \
--to=bmasney@redhat$(echo .)com \
--cc=heiko@sntech$(echo .)de \
--cc=justinstitt@google$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-clk@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=morbo@google$(echo .)com \
--cc=mturquette@baylibre$(echo .)com \
--cc=nathan@kernel$(echo .)org \
--cc=nick.desaulniers+lkml@gmail$(echo .)com \
--cc=rosenp@gmail$(echo .)com \
--cc=sboyd@kernel$(echo .)org \
/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