From: Stephen Boyd <sboyd@kernel.org>
To: Yixun Lan <dlan@gentoo.org>
Cc: Yixun Lan <dlan@gentoo.org>,
Michael Turquette <mturquette@baylibre.com>,
Guodong Xu <guodong@riscstar.com>,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] clk: spacemit: Updates for v6.20
Date: Wed, 21 Jan 2026 12:09:34 -0700 [thread overview]
Message-ID: <176902257445.4027.5972559722832621691@lazor> (raw)
In-Reply-To: <20260114092742-GYC7933267@gentoo.org>
Quoting Yixun Lan (2026-01-13 18:43:33)
>
> Hi Stephen,
>
> Please pull SpacemiT's clock changes for v6.20, This PR basically adds
> support for SpacemiT new K3 SoC, while doing this I've created an immutable
> tag (spacemit-clkrst-v6.20-3) for reset driver in case it also needs to be
> merged during same merge window, otherwise everything is normal.
>
> Yixun Lan
>
>
> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
>
> Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
>
> are available in the Git repository at:
>
> https://github.com/spacemit-com/linux tags/spacemit-clk-for-6.20-1
>
> for you to fetch changes up to e371a77255b837f5d64c9d2520f87e41ea5350b9:
>
> clk: spacemit: k3: add the clock tree (2026-01-09 10:48:17 +0800)
>
> ----------------------------------------------------------------
Thanks. Pulled into clk-next
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-01-21 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 1:43 [GIT PULL] clk: spacemit: Updates for v6.20 Yixun Lan
2026-01-21 19:09 ` Stephen Boyd [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=176902257445.4027.5972559722832621691@lazor \
--to=sboyd@kernel.org \
--cc=dlan@gentoo.org \
--cc=guodong@riscstar.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=spacemit@lists.linux.dev \
/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