From: Stephen Boyd <sboyd@kernel.org>
To: Haylen Chu <heylenay@4d2.org>, Yixun Lan <dlan@gentoo.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Haylen Chu <heylenay@outlook.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
spacemit@lists.linux.dev, Inochi Amaoto <inochiama@outlook.com>,
Chen Wang <unicornxdotw@foxmail.com>,
Jisheng Zhang <jszhang@kernel.org>,
Meng Zhang <zhangmeng.kevin@linux.spacemit.com>
Subject: Re: [PATCH v7 0/6] Add clock controller support for SpacemiT K1
Date: Tue, 29 Apr 2025 13:49:14 -0700 [thread overview]
Message-ID: <deb072638716e9978bd6381352cc721b@kernel.org> (raw)
In-Reply-To: <20250415004612-GYB29591@gentoo>
Quoting Yixun Lan (2025-04-14 17:46:12)
> Hi Haylen Chu:
> I'm quite happy with this version, as all the issues are solved,
> Thanks for working on this. I will give my RY and start to queue them.
>
> Hi Stephen Boyd,
> My plan to send a PR for inclusion to the clk tree in the 6.16
> merge window. But, let me know if there is still problem I overlooked.
You should send the code now. The merge window is when subsystem
maintainers like me send code to Linus, not when SoC maintainers send
code to subsystem maintainers. Typically folks wait until around -rc5 or
-rc6 to send it for the next merge window.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-04-29 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 7:44 [PATCH v7 0/6] Add clock controller support for SpacemiT K1 Haylen Chu
2025-04-12 7:44 ` [PATCH v7 1/6] dt-bindings: soc: spacemit: Add spacemit,k1-syscon Haylen Chu
2025-04-12 7:44 ` [PATCH v7 2/6] dt-bindings: clock: spacemit: Add spacemit,k1-pll Haylen Chu
2025-04-12 7:44 ` [PATCH v7 3/6] clk: spacemit: Add clock support for SpacemiT K1 SoC Haylen Chu
2025-04-14 18:12 ` Alex Elder
2025-04-14 21:43 ` Yixun Lan
2025-04-15 1:00 ` Inochi Amaoto
2025-04-12 7:44 ` [PATCH v7 4/6] clk: spacemit: k1: Add TWSI8 bus and function clocks Haylen Chu
2025-04-12 7:44 ` [PATCH v7 5/6] riscv: dts: spacemit: Add clock tree for SpacemiT K1 Haylen Chu
2025-04-12 7:44 ` [PATCH v7 6/6] riscv: defconfig: spacemit: enable clock controller driver " Haylen Chu
2025-04-14 18:12 ` Alex Elder
2025-04-15 0:53 ` Inochi Amaoto
2025-04-15 0:46 ` [PATCH v7 0/6] Add clock controller support " Yixun Lan
2025-04-29 20:49 ` Stephen Boyd [this message]
2025-04-30 0:54 ` 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=deb072638716e9978bd6381352cc721b@kernel.org \
--to=sboyd@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=heylenay@4d2.org \
--cc=heylenay@outlook.com \
--cc=inochiama@outlook.com \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=unicornxdotw@foxmail.com \
--cc=zhangmeng.kevin@linux.spacemit.com \
/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