Linux clock framework development
 help / color / mirror / Atom feed
From: "Rosen Penev" <rosenp@gmail.com>
To: "Brian Masney" <bmasney@redhat.com>, "Rosen Penev" <rosenp@gmail.com>
Cc: <linux-clk@vger.kernel.org>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"David Lechner" <david@lechnology.com>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv3] clk: davinci: add COMPILE_TEST support
Date: Wed, 02 Sep 2026 15:20:36 -0700	[thread overview]
Message-ID: <DL56IA99IWH9.22TJJI2Z54XM8@gmail.com> (raw)
In-Reply-To: <apidn5onRt_p4FOL@redhat.com>

On Wed Sep 2, 2026 at 3:05 PM PDT, Brian Masney wrote:
> Hi Rosen,
>
> On Wed, Aug 12, 2026 at 11:40:01AM -0700, Rosen Penev wrote:
>> Add a driver-scoped Kconfig symbol for the DaVinci clock drivers so
>> they can be built through COMPILE_TEST without selecting the ARM
>> DaVinci platform symbols.
>>
>> Keep the existing ARM platform behavior by defaulting the new symbol
>> from ARCH_DAVINCI, and use it for the davinci clock Makefile entries.
>> ARCH_DAVINCI_DA850 is the only remaining DaVinci platform symbol, so a
>> single COMMON_CLK_DAVINCI symbol suffices; the whole directory builds
>> together just fine.
>>
>> 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 against the latest clk tree. Can you post a new
> version that applies? I'll be able to pick it up.
Sent v4.
>
> Thanks,
>
> Brian


      reply	other threads:[~2026-09-02 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 18:40 [PATCHv3] clk: davinci: add COMPILE_TEST support Rosen Penev
2026-09-02 22:05 ` Brian Masney
2026-09-02 22:20   ` Rosen Penev [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=DL56IA99IWH9.22TJJI2Z54XM8@gmail.com \
    --to=rosenp@gmail.com \
    --cc=bmasney@redhat.com \
    --cc=david@lechnology.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.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