From: Yixun Lan <dlan@gentoo.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Alex Elder <elder@riscstar.com>,
linux-clk@vger.kernel.org, spacemit@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Immutable tag between SpacemiT's reset and clock trees for v6.17
Date: Thu, 3 Jul 2025 15:18:23 +0000 [thread overview]
Message-ID: <20250703151823-GYA312602@gentoo> (raw)
Hi Philipp,
Please pull the following change into the reset tree. This
allows you to apply the patch 5 of the SpacemiT reset driver [1].
Thanks,
Yixun Lan
Link: https://lore.kernel.org/r/20250702113709.291748-6-elder@riscstar.com [1]
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
https://github.com/spacemit-com/linux tags/spacemit-reset-binding-for-6.17-1
for you to fetch changes up to 25a59e813cd2ca728047f657d64f9b29480be393:
dt-bindings: soc: spacemit: define spacemit,k1-ccu resets (2025-07-03 22:16:08 +0800)
----------------------------------------------------------------
RISC-V SpacemiT Binding for 6.17
- Reset DT Binding for K1 SoC
----------------------------------------------------------------
Alex Elder (1):
dt-bindings: soc: spacemit: define spacemit,k1-ccu resets
.../bindings/soc/spacemit/spacemit,k1-syscon.yaml | 27 +++-
include/dt-bindings/clock/spacemit,k1-syscon.h | 141 +++++++++++++++++++++
2 files changed, 162 insertions(+), 6 deletions(-)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-07-03 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 15:18 Yixun Lan [this message]
2025-07-04 10:02 ` [GIT PULL] Immutable tag between SpacemiT's reset and clock trees for v6.17 Philipp Zabel
2025-07-06 4:06 ` Yixun Lan
2025-07-07 9:46 ` Philipp Zabel
2025-07-07 10:44 ` Yixun Lan
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=20250703151823-GYA312602@gentoo \
--to=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--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