From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 48725106FD60 for ; Fri, 13 Mar 2026 01:19:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=argiJVx6SL3Qgq8RlelY174zIXIz0UEsZ0+FVjxrboE=; b=zuvSHpoG1OmfRt ItKqbF2M3TGEGN4xVd8tCEXVBF7JD0V9J7kEamqvdehslsh/rNS3PzWG2im3dLP56cJd9MTh75bJW ZZ1tchF54c9CfcEd/oy7eGN6iDfh/Q8kmK34X6gNV09a1uK6CCgaYJ+g8M56VX5iJFbXG61c8eLwu KKn1v+KutIMJMly4sP9ENg6Gdxn0h/6FLU9hOpXgTXpDcYq2briA8E730dPdcuF2vUnUTzddPmzrs JsF3MSgR1qPlMQdHm0ByMFIz01uHer362l0E0fbONw2xeR6onXqP28b5VWAo6SBnDaognS6I2k8gH ZQPytBiQOh1imCOvkNhA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1w0rBL-0000000G3ef-2hgc; Fri, 13 Mar 2026 01:19:15 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1w0rBK-0000000G3eN-2QGO for linux-riscv@lists.infradead.org; Fri, 13 Mar 2026 01:19:14 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id A5F5C61334; Fri, 13 Mar 2026 01:19:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6632BC4CEF7; Fri, 13 Mar 2026 01:19:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773364753; bh=DBlu2vYwHqk1j0AVAu14WX3YgH/5nx3xXS/Du3SQ55k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uFM+G/a0xcVM1z3FJ17Y5s/3i6Xgajsz7uByrp0BRn5kVkbe3I+ANdAsdzwRQLa+T VDwpsUB2xt7OnlEtVw8yEe53cAVzHYaeotZetXoqaAXnrdV53yT6OOHukZUSkJ5NNS YdtpN750zHp8D8cQEcZsYZ0QSt21EfC1aITVm+UGE0MOqaFA7OAs7Mi9P1zWBZiE1D aTldv4Zpee3Y8UFcAmPlH0ubKQRZLODu/WwqvMSW3PN0uenzi1+8aOiDdBNBGN4Y5q AWj6XL+hZTVIzIS908fjAnumimaFxxlPbZfGbUBJhk+YH9nwGJS+3G/XJD9GYXt2YK BqzxIrbneatCQ== Date: Fri, 13 Mar 2026 09:19:10 +0800 From: Yixun Lan To: Greg Kroah-Hartman Cc: Yixun Lan , Jiri Slaby , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Lubomir Rintel , devicetree@vger.kernel.org, Guodong Xu , Conor Dooley , linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, linux-riscv@lists.infradead.org, spacemit@lists.linux.dev Subject: Re: [PATCH] dt-bindings: serial: 8250: spacemit: fix clock property for K3 SoC Message-ID: <20260313011910-GKL302167@kernel.org> References: <20260304-01-uart-clock-names-v1-1-338483f04a8b@kernel.org> <20260310093446-GYC318052@gentoo.org> <2026031226-utter-spellbind-53bf@gregkh> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <2026031226-utter-spellbind-53bf@gregkh> X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org Hi Greg, On 15:13 Thu 12 Mar , Greg Kroah-Hartman wrote: > On Tue, Mar 10, 2026 at 05:34:46PM +0800, Yixun Lan wrote: > > Hi Greg, Jiri, > > > > Do you mind if I taking this patch via SpacemiT's SoC tree? and if > > possible, it would be nice to have your Acks.. > > (or either way works for me, if you grab it and merged via tty tree) > > > > On 07:19 Wed 04 Mar , Yixun Lan wrote: > > > The UART of SpacemiT K3 SoC has same clock property as K1 generation which > > > request two clock sources, fix the binding otherwise will get DT check > > > warnings. > > > > > > Fixes: b5024e804ee0 ("dt-bindings: serial: 8250: add SpacemiT K3 UART compatible") > > I would just drop the Fixes tag, as I think at the time of Gudong > > submitting the patch, the clock driver isn't ready, so he deliberatly > > removed this clock contraint and provided with a fixed clock frequency > > (the bindings match with DTS) > > > > https://github.com/torvalds/linux/blob/v7.0-rc3/arch/riscv/boot/dts/spacemit/k3.dtsi#L414 > > You need to get a DT maintainer to review it before you can apply it. Ok, so Rob gave an Ack > If you want to take it through your tree once that happens, that's fine > with me. Thanks, so this imply an Ack, but could give an explict Acked-by? then I will proceed.. -- Yixun Lan (dlan) _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv