From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D948B1362 for ; Sun, 6 Jul 2025 04:06:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=140.211.166.183 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751774818; cv=none; b=JgTUbCMtAzR9hBh+bCtEPcu3G0bLs9OnNaIM595J+BcYwsuMf7Xw9uxjq9McyoqvDJsbruB8WTSnxhv+6MoUCEd/OzUxsAnpeF8AZOVVnuibdO3Dl2Ohe2xvuXRH4XQzgIJAiLrtB9QyRKIz2kSTYVFllpfKZCBc/RYJGfiYuKI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751774818; c=relaxed/simple; bh=ZvnxcHwiDjSH4zYWbfszHUNhAOzWLerR0q8cLLZfR0Y=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Lnbzh3tEruBWvP3peVr6AKLPlSpSefSmCbRfMo17QQjkfCy+sYsa62B7g+THH1aj2TE/zJFVsP5FxJ3AYZ/ne8B0LgUOB+tW3Xb0ZGOKKmhkkFPXwheYT5ioKl83PcSArY823HBxpVSUorGrMFSd+TlmxDMWxBX7/OuYzKBNSRg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gentoo.org; spf=pass smtp.mailfrom=gentoo.org; arc=none smtp.client-ip=140.211.166.183 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gentoo.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gentoo.org Received: from localhost (unknown [116.232.48.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange secp256r1 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: dlan) by smtp.gentoo.org (Postfix) with ESMTPSA id D67A7341EC0; Sun, 06 Jul 2025 04:06:55 +0000 (UTC) Date: Sun, 6 Jul 2025 04:06:46 +0000 From: Yixun Lan To: Philipp Zabel Cc: Stephen Boyd , Michael Turquette , Alex Elder , linux-clk@vger.kernel.org, spacemit@lists.linux.dev, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] Immutable tag between SpacemiT's reset and clock trees for v6.17 Message-ID: <20250706040646-GYA408198@gentoo> References: <20250703151823-GYA312602@gentoo> Precedence: bulk X-Mailing-List: spacemit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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)