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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E31BBC433F5 for ; Wed, 1 Jun 2022 06:03:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349801AbiFAGDX (ORCPT ); Wed, 1 Jun 2022 02:03:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52396 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243177AbiFAGDT (ORCPT ); Wed, 1 Jun 2022 02:03:19 -0400 Received: from mailbox.box.xen0n.name (mail.xen0n.name [115.28.160.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 15C4864D0D; Tue, 31 May 2022 23:03:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xen0n.name; s=mail; t=1654062778; bh=+SQ/0eJGKRfUjrv0y7MBl6u9+aie9yNgtn9zXiJXatQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=MPrVk57osmnSJSH8usd6C0hOYOQnqvMfimKla8SPTKb1b3p7S7z4TV3QbmJvgi8wz QvqDrG+EPygWMfJumqmcMARAyrD4yUYS9QesvYMzOhDspws14XkxFR1mG0+D9SYk4H PbOG71wY9849hZUFfXVpJ1HsxE8Qs6miB8t2TYJA= Received: from [192.168.9.172] (unknown [101.88.28.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailbox.box.xen0n.name (Postfix) with ESMTPSA id 9FFC260104; Wed, 1 Jun 2022 13:52:57 +0800 (CST) Message-ID: <832c3ae8-6c68-db2c-2c7f-0a5cd3071543@xen0n.name> Date: Wed, 1 Jun 2022 13:52:57 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Thunderbird/103.0a1 Subject: Re: [musl] Re: [GIT PULL] asm-generic changes for 5.19 Content-Language: en-US To: Huacai Chen , Arnd Bergmann Cc: musl@lists.openwall.com, WANG Xuerui , Linus Torvalds , linux-arch , GNU C Library , Yoshinori Sato , Peter Zijlstra , Marc Zyngier , Masahiro Yamada , Linux Kernel Mailing List , Jiaxun Yang , ACPI Devel Maling List , Jianmin Lv , linux-pci , Ard Biesheuvel , Huacai Chen References: <358025d1-28e6-708b-d23d-3f22ae12a800@xen0n.name> From: WANG Xuerui In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/1/22 00:01, Huacai Chen wrote: > https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/log/?h=loongarch-next > has been updated. Now this branch droped irqchip drivers and pci > drivers. But the existing irqchip drivers need some small adjustment > to avoid build errors [1], and I hope Marc can give an Acked-by. > Thanks. > > This branch can be built with defconfig and allmodconfig (except > drivers/platform/surface/aggregator/controller.c, because it requires > 8bit/16bit cmpxchg, which I was told to remove their support). > > [1] https://lore.kernel.org/lkml/e7cf33a170d0b4e98e53744f60dbf922@kernel.org/T/#t I see the loongarch-next HEAD has been updated and it's now purely arch changes aside from the two trivial irqchip cleanups. Some other changes to the v11 patchset [1] are included, but arguably minor enough to not invalidate previous Reviewed-by tags. After some small tweaks: - adding "#include " to arch/loongarch/include/asm/ptrace.h, - adding an arch/loongarch/include/uapi/asm/bpf_perf_event.h with the same content as arch/arm64's, and - adding "depends on ARM64 || X86" to drivers/platform/surface/aggregator/Kconfig, the current loongarch-next HEAD (commit 36552a24f70d21b7d63d9ef490561dbdc13798d7) now passes allmodconfig build (with CONFIG_WERROR disabled; my Gentoo-flavored gcc-12 seems to emit warnings on a few drivers). The majority of userspace ABI has been stable for a few months already, after the addition of orig_a0 and removal of newfstatat; the necessary changes to switch to statx are already reviewed [2] / merged [3], and have been integrated into the LoongArch port of Gentoo for a while. Eric looked at the v11 and gave comments, and changes were made according to the suggestions, but it'd probably better to get a proper Reviewed-by. Among the rest of patches, I think maybe the EFI/boot protocol part still need approval/ack from the EFI maintainer. However because the current port isn't going to be able to run on any real hardware, maybe that part could be done later; I'm not sure if the unacknowledged EFI bits should be removed as well. Arnd, what do you think about the current branch's status? Do Huacai need to send a quick final v12 to gather tags? [1]: https://lore.kernel.org/all/20220518092619.1269111-1-chenhuacai@loongson.cn/ [2]: https://sourceware.org/pipermail/libc-alpha/2022-May/139127.html [3]: https://go-review.googlesource.com/c/go/+/407694