From: Drew Fustini <fustini@kernel.org>
To: Brian Masney <bmasney@redhat.com>
Cc: Rosen Penev <rosenp@gmail.com>,
linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:CLANG/LLVM BUILD SUPPORT:Keyword:b(?i:clang|llvm)b"
<llvm@lists.linux.dev>
Subject: Re: [PATCHv2] clk: thead: allow COMPILE_TEST builds
Date: Wed, 8 Jul 2026 23:30:10 -0700 [thread overview]
Message-ID: <ak8/8ixE7IS7kKdz@x1> (raw)
In-Reply-To: <ak0T7zxwwSn_L57X@redhat.com>
On Tue, Jul 07, 2026 at 10:57:51AM -0400, Brian Masney wrote:
> On Mon, Jul 06, 2026 at 05:56:19PM -0700, Rosen Penev wrote:
> > Follow the pattern of many other directories in this Makefile (sunxi-ng,
> > tenstorrent, ti, etc.) by using obj-y. This allows COMPILE_TEST to
> > select the driver without having CONFIG_ARCH_THEAD enabled
> >
> > Tested with:
> > make LLVM=1 ARCH=loongarch drivers/clk/thead/
> >
> > Assisted-by: Codex:GPT-5.5
> > Signed-off-by: Rosen Penev <rosenp@gmail.com>
>
> Reviewed-by: Brian Masney <bmasney@redhat.com>
This doesn't apply to 7.2-rc or next for me due to the surrounding
context, but I agree with the change itself.
Acked-by: Drew Fustini <fustini@kernel.org>
Brian - do you think this should be routed through my thead-clk tree or
go through the main clk tree?
Thanks,
Drew
next prev parent reply other threads:[~2026-07-09 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 0:56 [PATCHv2] clk: thead: allow COMPILE_TEST builds Rosen Penev
2026-07-07 14:57 ` Brian Masney
2026-07-09 6:30 ` Drew Fustini [this message]
2026-07-09 12:05 ` Brian Masney
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=ak8/8ixE7IS7kKdz@x1 \
--to=fustini@kernel.org \
--cc=bmasney@redhat.com \
--cc=justinstitt@google.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=mturquette@baylibre.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=rosenp@gmail.com \
--cc=sboyd@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