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 96B0DC433F5 for ; Mon, 30 May 2022 13:01:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236284AbiE3NBq (ORCPT ); Mon, 30 May 2022 09:01:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39188 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233847AbiE3NBn (ORCPT ); Mon, 30 May 2022 09:01:43 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 95A885F94; Mon, 30 May 2022 06:01:39 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 333C060DD8; Mon, 30 May 2022 13:01:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9256DC3411F; Mon, 30 May 2022 13:01:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1653915698; bh=P31uo602B0Lw3sp32uTNYyaSbPsuU19TeHSt9/MJjyI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=fAaR0zTawFiHbHpKN5pzKPk+m99MGmCVzLz5sm2Oe043iPI2mRlzm19OnVfUGJQ+q hjxqRzlOaEDqfGDhQFcQEOhENj41lCAx82me6SDWpaH0BBVWcSrZWGtRvkaSIE5PsN Nta3N/ZMKjhueE68+BCp74+MUB3+Sz/0D9vicpRX8np6E/nv1P/fZIntobbe62/bDz GNMqfnu6OgS2CZ3bQ4/+OEayxmysUqlvUSLHvrfIhkzGcB0M/om5Av6hWX0OM+DGWw O91gx/9RQjXjm5n+F1tpfSNGqXhMI8NvX3nxxE9zXgNjd0Ux8Ig3YntNQcdmg3rBg7 2lrCDG/rRUW7g== Received: by mail-ua1-f54.google.com with SMTP id q1so3804844uao.1; Mon, 30 May 2022 06:01:38 -0700 (PDT) X-Gm-Message-State: AOAM533s12IQrVDKYy3h8/CHc6vkZO6URorwOlORD3S/W1VULj8JazVN FKCduYhwEhwkXh/7OdAUTJ31rBapEyqeR36qEho= X-Google-Smtp-Source: ABdhPJyhqQ9qgd1r5/qcNoED52QOHpIhyWBhd2usCvKUVn8AsyE5OajEl3nhKMAILqXIBpnc17BmTEG5fiUwQuc9EqE= X-Received: by 2002:ab0:2bc9:0:b0:362:8750:8032 with SMTP id s9-20020ab02bc9000000b0036287508032mr19067906uar.118.1653915697481; Mon, 30 May 2022 06:01:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Huacai Chen Date: Mon, 30 May 2022 21:01:25 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [GIT PULL] asm-generic changes for 5.19 To: 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org 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. Huacai > > 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