mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: musl@lists.openwall.com
Cc: Marc Zyngier <maz@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 linux-arch <linux-arch@vger.kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	Huacai Chen <chenhuacai@loongson.cn>,
	 WANG Xuerui <kernel@xen0n.name>,
	libc-alpha@sourceware.org,  Ard Biesheuvel <ardb@kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	 linux-pci <linux-pci@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	 Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [musl] Re: [GIT PULL] asm-generic changes for 5.19
Date: Mon, 30 May 2022 10:36:46 +0200	[thread overview]
Message-ID: <CAK8P3a0aQO2rOVD0F6w811z6ooeGcmLd4UkpPK7dX_SGGy7WDw@mail.gmail.com> (raw)
In-Reply-To: <CAAhV-H4icDqABQiT4ckKdsmfVzqBKjxncDt9649c2ijOD093gw@mail.gmail.com>

On Mon, May 30, 2022 at 8:28 AM Huacai Chen <chenhuacai@kernel.org> wrote:
> On Sun, May 29, 2022 at 9:21 PM Marc Zyngier <maz@kernel.org> wrote:
> > On Sun, 29 May 2022 12:24:29 +0100, Arnd Bergmann <arnd@kernel.org> wrote:
> >
> > I'd tend to agree. But if on the other hand the userspace ABI is
> > clearly defined, I think it could make sense to go for it (if I
> > remember well, we merged arm64 without any support irqchip support,
> > and the arm64 GIC support appeared later in the game).
> (adding linux-pci and linux-acpi maintainers to Cc)
>
> I'd like to confirm the review status of the respective LoongArch
> patchsets ([1], [2]), to see if we can make it into this merge window.

In the meantime, can you rebase the tree once more to split out the
driver patches and make sure the architecture port without the drivers
still builds cleanly (at least defconfig and allmodconfig) using the compiler
from [1]? If this requires additional patches, please add them on top.

Once that is done, we can ask Linus to consider merging the branch
for the architecture port, while you keep working with the pci and irqchip
maintainers to merge the drivers either for 5.19 or a future release.

While this means merging a branch that does not actually work on any
hardware by itself, it should be sufficient for the libc patches to
consider the ABI stable, and it is consistent with how we keep
CPU architecture support separate from platform driver support
elsewhere.

       Arnd

[1] https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/12.1.0/x86_64-gcc-12.1.0-nolibc-loongarch64-linux.tar.xz

  reply	other threads:[~2022-05-30  8:37 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
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 [this message]
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=CAK8P3a0aQO2rOVD0F6w811z6ooeGcmLd4UkpPK7dX_SGGy7WDw@mail.gmail.com \
    --to=arnd@kernel.org \
    --cc=ardb@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=chenhuacai@loongson.cn \
    --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=masahiroy@kernel.org \
    --cc=maz@kernel.org \
    --cc=musl@lists.openwall.com \
    --cc=palmer@dabbelt.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.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).