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 B8F1DE7717F for ; Thu, 12 Dec 2024 10:19:21 +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=Zyc9/3hPsqfIj7I7aDPZyiQgqs93FVWxor1tP7xI/oA=; b=rJo0I656D5YXGy o5XdvtFvu/7YHWEWzJ+fJbJ3CNqhLtQ3Rf9lA2L8GFTqQ1685dDLC8tEXEkQGVaO2FVjWMgREZQXv u4EjtyYY5R1Y9lbQ4T3a5QvUBTOh7ky0STXlRAWT4eFer2wVWd2vm7yC6zJhPTHYcKGti8cQy8wIo +fSdUSALvqGd2UV24qPrekK6k5osqV3v8St4Ksh2fswyuEQD/yVhWxADjYE4E94OMs3Qzo5j+iOzs BDGXwK7Pr1H7+oXhHkUfha2z/H1xD93FqIL/WtawBKFemRMMoqvGE72rcuuQy4keh2ImeuXqQuj9F FhEeceLQjLRjwvtiRc+Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1tLgHr-0000000028f-2tym; Thu, 12 Dec 2024 10:19:15 +0000 Received: from woodpecker.gentoo.org ([140.211.166.183] helo=smtp.gentoo.org) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1tLgHp-0000000028D-2tkA for linux-riscv@lists.infradead.org; Thu, 12 Dec 2024 10:19:14 +0000 Date: Thu, 12 Dec 2024 18:19:01 +0800 From: Yixun Lan To: Conor Dooley Cc: linux-riscv@lists.infradead.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, cyy@cyyself.name, daniel.lezcano@linaro.org, tglx@linutronix.de, samuel.holland@sifive.com, anup@brainfault.org, gregkh@linuxfoundation.org, jirislaby@kernel.org, lkundrak@v3.sk, devicetree@vger.kernel.org, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, Jesse Taube , inochiama@outlook.com, zhangmeng.kevin@spacemit.com, jszhang@kernel.org, matthias.bgg@kernel.org, kevin.z.m@hotmail.com Subject: Re: [PATCH v5 00/10] riscv: add initial support for SpacemiT K1 Message-ID: <20241212101901-GYA2292414@gentoo> References: <20240730-k1-01-basic-dt-v5-0-98263aae83be@gentoo.org> <173395638199.1729195.1529576042123666894.git-patchwork-notify@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <173395638199.1729195.1529576042123666894.git-patchwork-notify@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241212_021913_755891_B4ABFD10 X-CRM114-Status: GOOD ( 17.00 ) 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 Conor: On 22:33 Wed 11 Dec , patchwork-bot+linux-riscv@kernel.org wrote: > Hello: > > This series was applied to riscv/linux.git (fixes) > by Conor Dooley : > > On Tue, 30 Jul 2024 00:28:03 +0000 you wrote: > > SpacemiT K1 is an ideal chip for some new extension such as RISC-V Vector > > 1.0 and Zicond evaluation now. Add initial support for it to allow more > > people to participate in building drivers to mainline for it. > > > > This kernel has been tested upon Banana Pi BPI-F3 board on vendor U-Boot > > bootflow generated by Armbian SDK[1] and patched OpenSBI[2] to enable > > Zicboz, which does not in the vendor dts on its U-Boot. Then successfully > > booted to busybox on initrd with this log[3]. > > > > [...] > > Here is the summary with links: > - [v5,01/10] dt-bindings: vendor-prefixes: add spacemit > https://git.kernel.org/riscv/c/7cf3e9bfc63d If I understand correctly, only patch [01/10] of this series was accepted to 6.13-rc1 for the rest of patches, they would be expected to go through SpacemiT's SoC tree? which should I take care of them.. so if no objection, I'd like to queue them at branch k1/dt-for-next [1] first, we might rebase or revert if something happens before merging (since the clock driver is still under review) Let me know what you think.. Link: https://github.com/spacemit-com/linux/tree/k1/dt-for-next [1] > - [v5,02/10] dt-bindings: riscv: Add SpacemiT X60 compatibles > (no matching commit) > - [v5,03/10] dt-bindings: riscv: add SpacemiT K1 bindings > (no matching commit) > - [v5,04/10] dt-bindings: timer: Add SpacemiT K1 CLINT > (no matching commit) > - [v5,05/10] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC > (no matching commit) > - [v5,06/10] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible > (no matching commit) > - [v5,07/10] riscv: add SpacemiT SoC family Kconfig support > (no matching commit) > - [v5,08/10] riscv: dts: add initial SpacemiT K1 SoC device tree > (no matching commit) > - [v5,09/10] riscv: dts: spacemit: add Banana Pi BPI-F3 board device tree > (no matching commit) > - [v5,10/10] riscv: defconfig: enable SpacemiT SoC > (no matching commit) > > You are awesome, thank you! > -- > Deet-doot-dot, I am a bot. > https://korg.docs.kernel.org/patchwork/pwbot.html > > -- Yixun Lan (dlan) Gentoo Linux Developer GPG Key ID AABEFD55 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv