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 28690 invoked from network); 30 May 2022 15:00:42 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 30 May 2022 15:00:42 -0000 Received: (qmail 11715 invoked by uid 550); 30 May 2022 15:00:39 -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 11675 invoked from network); 30 May 2022 15:00:38 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xen0n.name; s=mail; t=1653922822; bh=s1QiOz9wspSFr3MKcctc4iYPmhaFi0B1Ir77QXPhGkQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=XfTYcoObJmrg/JDjGJc1MTn8iRm6p9KRmLhJGb19BxuVDXKKtNE0cQ2gWHsF9L+p0 dIpeX7wWK2a9S4ui6qfeVUc2FQZiqJyJIw5ZbLpSGeapzW6+8zzFTniivYOrQZqCSp 2f7dkspWYhoyPbx9PLNCS+9mqHuvG4xR3MX9aq/M= Message-ID: <358025d1-28e6-708b-d23d-3f22ae12a800@xen0n.name> Date: Mon, 30 May 2022 23:00:21 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.0a1 To: Huacai Chen , Arnd Bergmann Cc: WANG Xuerui , Linus Torvalds , linux-arch , libc-alpha@sourceware.org, Yoshinori Sato , Peter Zijlstra , Marc Zyngier , Masahiro Yamada , musl@lists.openwall.com, Linux Kernel Mailing List , Jiaxun Yang , ACPI Devel Maling List , Jianmin Lv , linux-pci , Ard Biesheuvel , Huacai Chen References: Content-Language: en-US From: WANG Xuerui In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [musl] Re: [GIT PULL] asm-generic changes for 5.19 On 5/30/22 21:01, Huacai Chen wrote: > Hi, Arnd, > > On Mon, May 30, 2022 at 4:21 PM Arnd Bergmann wrote: >> On Sun, May 29, 2022 at 3:10 PM WANG Xuerui wrote: >>> But what for the users and downstream projects? Do the users owning >>> LoongArch hardware (me included) and projects/companies porting their >>> offerings have to pay for Loongson's mistakes and wait another [2mo, >>> 1yr], "ideally" also missing the glibc 2.36 release too? >> ... >>> Lastly, I'd like to clarify, that this is by no means a >>> passive-aggressive statement to make the community look like "the bad >>> guy", or to make Loongson "look bad"; I just intend to provide a >>> hopefully fresh perspective from a/an {end user, hobbyist kernel >>> developer, distro developer, native Chinese speaker with a hopefully >>> decent grasp of English}'s view. >> Your feedback has been extremely valuable, as always. I definitely >> don't want to hold up merging the port for the glibc-2.36 release. If >> that is a risk, and if merging the architecture port without the drivers >> helps with that, I agree we should just do that. This will also help >> with build testing and any treewide changes that are going to be >> done on top of v5.19-rc1. >> >> For the continuous maintenance, would you be available as an >> additional Reviewer or co-maintainer to be listed in the maintainers >> file? I think in general it is a good idea to have at least one maintainer >> that is not directly part of the organization that owns the product, >> and you are clearly the best person outside of loongson technology >> for this. > Yes, Xuerui is very suitable as a Reviewer. Thanks for the recognition from both of you; it is my honor and pleasure to contribute to the LoongArch port and to Linux in general. As I'm still not entirely satisfied with my kernel development skills, plus my day job is not kernel-related nor Loongson/LoongArch-related at all, listing me as reviewer should be enough for now. I will take care of the arch as long as I have the hardware. BTW, there were already several breakages when rebasing the previous revision (I believe it's commit 215da6d2dac0 ("MAINTAINERS: Add maintainer information for LoongArch")) on top of linus' tree. Now I see the loongarch-next HEAD is already rebased on top of what I believe to be the current main branch, however I vaguely remember that it's not good to base one's patches on top of "some random commit", so I wonder whether the current branch state is appropriate for a PR?