linux-kernel - Re: [GIT PULL] Immutable tag between SpacemiT's reset and clock trees for v6.17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250706040646-GYA408198@gentoo>
Date: Sun, 6 Jul 2025 04:06:46 +0000
From: Yixun Lan <dlan@...too.org>
To: Philipp Zabel <p.zabel@...gutronix.de>
Cc: Stephen Boyd <sboyd@...nel.org>,
	Michael Turquette <mturquette@...libre.com>,
	Alex Elder <elder@...cstar.com>, linux-clk@...r.kernel.org,
	spacemit@...ts.linux.dev, linux-riscv@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Immutable tag between SpacemiT's reset and clock
 trees for v6.17

Hi Philipp,

On 12:02 Fri 04 Jul     , Philipp Zabel wrote:
> On Do, 2025-07-03 at 15:18 +0000, Yixun Lan wrote:
> > 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]
> 
> Sorry I didn't notice before, this is missing k1-syscon.h from Patch 2.
>  
no problem

> Can we get a clock maintainer ack to place patch 2 in the shared tag as
> well? Otherwise you could split patch 2 into soc and clk parts.
for the ack, I'd assume Stephen have no objection (Cc him explicitly)

technically, there is no problem to place more patches in the shared
tag, since the tag will be both sent(by me) to clock and reset tree,
so no conflicts in the end.

if you expect to at least pass compiling test with patch 5 in reset
branch only, then patch 1, 2, 3 should be included, otherwise need to
pull clk branch for additional dependency patches.

I would propose to have shared tag to include patch 1-4, then you can
pick patch 5, in this way, it should both pass all tests (both
compile-time and run-time)

what do you think?

-- 
Yixun Lan (dlan)