From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12755 invoked from network); 29 May 2022 13:46:25 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 29 May 2022 13:46:25 -0000 Received: (qmail 1155 invoked by uid 550); 29 May 2022 13:46:15 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 10218 invoked from network); 29 May 2022 13:21:49 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1653830496; bh=dxfYme49t+GbMgcSO3QeI/AUvVznk4CbVEjgcs5IqeA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ZtvYyGuKggkHRZd4Tuz79URyRouxrmYBBua0Sj4ctMAqerLnnHdoIaKrqigBEKqhu yo3F+UafQ2xlqmoX2615EZF0FRYj3B2o5NwUr1GawytpkyyWYDE7pUJz8KZRtu1qdp U7KEHKxx1mS68I/tPRFz70tePN3o5ED45GDZToadAUpFfGr44ti5zkbo0WQqh00rjW rW7vf+lITgBan3cYOyV6Bd8y6Mb6BgQCpL6lDnWqhEkGW5QmPz9wKElyAYDL2ZQXHD QVYnZt9Zd+Km7TGL4g5B6FX+b32Az4r2s9HDs9IUAU+vrpn5tSmN54cgW84fmKua8E Ixxu1y7kvkm0A== Date: Sun, 29 May 2022 14:21:33 +0100 Message-ID: <875ylomq3m.wl-maz@kernel.org> From: Marc Zyngier To: Arnd Bergmann Cc: Linus Torvalds , linux-arch , Linux Kernel Mailing List , Yoshinori Sato , Palmer Dabbelt , Masahiro Yamada , Peter Zijlstra , Huacai Chen , WANG Xuerui , libc-alpha@sourceware.org, musl@lists.openwall.com, ardb@kernel.org, linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: arnd@kernel.org, torvalds@linux-foundation.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, ysato@users.sourceforge.jp, palmer@dabbelt.com, masahiroy@kernel.org, peterz@infradead.org, chenhuacai@loongson.cn, kernel@xen0n.name, libc-alpha@sourceware.org, musl@lists.openwall.com, ardb@kernel.org, linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Subject: [musl] Re: [GIT PULL] asm-generic changes for 5.19 On Sun, 29 May 2022 12:24:29 +0100, Arnd Bergmann wrote: > > On Thu, May 26, 2022 at 5:00 PM Arnd Bergmann wrote: > > - A series to add a generic ticket spinlock that can be shared by most > > architectures with a working cmpxchg or ll/sc type atomic, including > > the conversion of riscv, csky and openrisc. This series is also a > > prerequisite for the loongarch64 architecture port that will come as > > a separate pull request. > > An update on Loongarch: I was originally planning to send Linus a > pull request with > the branch with the contents from > > https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/log/?h=loongarch-next > > but I saw that this includes both the architecture code and some > device drivers (irqchip, pci, acpi) that are essential for the > kernel to actually boot. At least the irqchip driver has not passed > review because it uses a nonstandard way to integrate into ACPI, and > the PCI stuff may or may not be ready but has no Reviewed-by or > Acked-by tags from the maintainers. I clearly don't want to bypass > the subsystem maintainers on those drivers by sending a pull request > for the current branch. It seems that there is now a new contributor on the irqchip front, and the current approach *should* be better than the "copy MIPS and run" approach that was previously taken. I'm still to find time to review the new series (I just came back from a week off), but hopefully next week. > My feeling is that there is also no point in merging a port without > the drivers as it cannot work on any hardware. On the other hand, > the libc submissions (glibc and musl) are currently blocked while > they are waiting for the kernel port to get merged. I'd tend to agree. But if on the other hand the userspace ABI is clearly defined, I think it could make sense to go for it (if I remember well, we merged arm64 without any support irqchip support, and the arm64 GIC support appeared later in the game). Thanks, M. -- Without deviation from the norm, progress is not possible.