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 13799 invoked from network); 30 May 2022 08:21:33 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 30 May 2022 08:21:33 -0000 Received: (qmail 28519 invoked by uid 550); 30 May 2022 08:21:31 -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 28486 invoked from network); 30 May 2022 08:21:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1653898877; bh=6mZJiJbmBP5nIWsu49+CXVUX8jQfK+UvVFjRNgWXebw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=XaoiQTO07UWKTKa7DvAu3E1TqyqCrZvDMjSawN2jqjs76oebLWXuHNyMMHpEHCuW2 RWVc8AQkaQdSALmWN1qEnP0U8+tmhvdUUIDC3u1bZpg/H6AlLeWXqRxTX/vimIu5bw OXy7mEv0vYi2vsR/WO2VshcjWhH9onv5cq3HaCOzUDMYDdSqutECZxfI+ZI4FnTXlx PNqKIZPahp6AyssPmubpmLdigj+1u+H946fyAVrYADTUucMm/fFuIBWV9X6L1Zmr14 QpLIbLZkXFgalB1GAGy3ay5uv7IuaVB4BOqOQrDUDblPJ+kvhE44AXYO5EfX0654Vb Oc99QbaK00vFw== X-Gm-Message-State: AOAM531JN1R936wPZn7WlZa08SVTSU0hnsFHbSn4ZXMcwjRPxdZoDB5S ccRLfsmcvgjjptqZ7ktPcqmfKDfwRbub4wgQKno= X-Google-Smtp-Source: ABdhPJwtYtcRJBvW0OhdeYiTGlxOaw+f4fu0VS7H8dnFKjbyUOJjLxz2DuwfUfrH0XZz0QtT75LFMu05vESNYppoiso= X-Received: by 2002:a81:488c:0:b0:302:549f:ffbc with SMTP id v134-20020a81488c000000b00302549fffbcmr21167071ywa.495.1653898876538; Mon, 30 May 2022 01:21:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Arnd Bergmann Date: Mon, 30 May 2022 10:20:59 +0200 X-Gmail-Original-Message-ID: Message-ID: To: WANG Xuerui Cc: 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 , linux-acpi@vger.kernel.org, Jianmin Lv , linux-pci@vger.kernel.org, ardb@kernel.org, Huacai Chen Content-Type: text/plain; charset="UTF-8" Subject: [musl] Re: [GIT PULL] asm-generic changes for 5.19 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. Regarding the irqchip driver, merging those is entirely up to Marc and Thomas. Marc already brought up the precedent of merging arch/arm64 without the required irqchip driver support, and if it turns out that he find the latest driver submission acceptable, that might still make it in through the irqchip tree. Arnd