mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Huacai Chen <chenhuacai@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 linux-arch <linux-arch@vger.kernel.org>,
	libc-alpha@sourceware.org,
	 Yoshinori Sato <ysato@users.sourceforge.jp>,
	Peter Zijlstra <peterz@infradead.org>,
	 Marc Zyngier <maz@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	musl@lists.openwall.com,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	 ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Jianmin Lv <lvjianmin@loongson.cn>,
	 linux-pci <linux-pci@vger.kernel.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	 Huacai Chen <chenhuacai@loongson.cn>
Subject: [musl] Re: [GIT PULL] asm-generic changes for 5.19
Date: Mon, 30 May 2022 21:01:25 +0800	[thread overview]
Message-ID: <CAAhV-H6sNr-yo8brBFtzziH6k9Tby0dFp7yehK55SfH5HjZ8hQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3awFdB1-G65DC38NBuSTvo6SvFTaS0m9YBxunHjHjQvQ@mail.gmail.com>

Hi, Arnd,

On Mon, May 30, 2022 at 4:21 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> On Sun, May 29, 2022 at 3:10 PM WANG Xuerui <kernel@xen0n.name> 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

  reply	other threads:[~2022-05-30 13:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK8P3a2_52JPnBWNvTTkFVwLxPAa7=NaQ4whwC1UeH_NYHeUKQ@mail.gmail.com>
2022-05-29 11:24 ` Arnd Bergmann
2022-05-29 13:10   ` WANG Xuerui
2022-05-30  8:20     ` Arnd Bergmann
2022-05-30 13:01       ` Huacai Chen [this message]
2022-05-30 15:00         ` WANG Xuerui
2022-05-30 15:55           ` Arnd Bergmann
2022-05-31  7:50             ` Huacai Chen
2022-05-31  8:09               ` Arnd Bergmann
2022-05-31  8:17                 ` Huacai Chen
2022-05-31 11:15                   ` Arnd Bergmann
2022-05-31 16:01                     ` Huacai Chen
2022-05-31 20:07                       ` Arnd Bergmann
2022-05-31 20:40                         ` Arnd Bergmann
2022-06-01  0:41                           ` WANG Xuerui
2022-06-01  1:13                         ` WANG Xuerui
2022-06-01  5:52                       ` WANG Xuerui
2022-06-01  7:41                         ` Arnd Bergmann
2022-06-01 16:01                           ` Ard Biesheuvel
2022-06-01 16:44                             ` WANG Xuerui
2022-06-02 10:02                               ` Huacai Chen
2022-05-29 13:21   ` Marc Zyngier
2022-05-30  6:28     ` Huacai Chen
2022-05-30  8:36       ` Arnd Bergmann
2022-05-30  8:23     ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAhV-H6sNr-yo8brBFtzziH6k9Tby0dFp7yehK55SfH5HjZ8hQ@mail.gmail.com \
    --to=chenhuacai@kernel.org \
    --cc=ardb@kernel.org \
    --cc=arnd@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lvjianmin@loongson.cn \
    --cc=masahiroy@kernel.org \
    --cc=maz@kernel.org \
    --cc=musl@lists.openwall.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ysato@users.sourceforge.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).