From: Brian Masney <bmasney@redhat.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: 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: [PATCH] clk: hisilicon: allow COMPILE_TEST builds
Date: Mon, 20 Jul 2026 10:53:28 -0400 [thread overview]
Message-ID: <al42aFXfvbPUIJAV@redhat.com> (raw)
In-Reply-To: <CAKxU2N9Wf07ZNvVyOz=WR+8TdzxoivnAp5x3_FN5rqpU6M7maw@mail.gmail.com>
Hi Rosen,
On Sun, Jul 19, 2026 at 02:44:03PM -0700, Rosen Penev wrote:
> On Mon, May 11, 2026 at 8:00 AM Brian Masney <bmasney@redhat.com> wrote:
> >
> > On Fri, May 08, 2026 at 10:11:10PM -0700, Rosen Penev wrote:
> > > The HiSilicon clock symbols already depend on ARCH_HISI or COMPILE_TEST,
> > > but the parent clock Makefile only descends into the hisilicon directory
> > > when ARCH_HISI is enabled.
> > >
> > > Add a hidden family gate selected by the HiSilicon clock and reset symbols,
> > > default it for ARCH_HISI, and use it for the parent Makefile descent. This
> > > keeps existing platform builds unchanged while allowing compile-test
> > > coverage.
> > >
> > > Tested with:
> > > make LLVM=1 ARCH=loongarch drivers/clk/hisilicon/
> > >
> > > Assisted-by: Codex:GPT-5.5
> > > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> >
> > Reviewed-by: Brian Masney <bmasney@redhat.com>
> Should I resend?
Yes, it missed the last merge window, and I submitted it to Stephen on
June 29th via this git pull:
https://lore.kernel.org/linux-clk/akLzCVzbMbUsgDda@redhat.com/T/#u
Let's see what he says. Hopefully you won't have to resend.
Brian
prev parent reply other threads:[~2026-07-20 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 5:11 [PATCH] clk: hisilicon: allow COMPILE_TEST builds Rosen Penev
2026-05-11 14:59 ` Brian Masney
2026-07-19 21:44 ` Rosen Penev
2026-07-20 14:53 ` Brian Masney [this message]
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=al42aFXfvbPUIJAV@redhat.com \
--to=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