[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0dcmeehX=ByKqFe_aa7=fJFjAfpCG6ch99BzK8N4FA2A@mail.gmail.com>
Date: Mon, 30 May 2022 10:23:41 +0200
From: Arnd Bergmann <arnd@...nel.org>
To: Marc Zyngier <maz@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, linux-arch <linux-arch@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Palmer Dabbelt <palmer@...belt.com>, Masahiro Yamada <masahiroy@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, Huacai Chen <chenhuacai@...ngson.cn>,
WANG Xuerui <kernel@...0n.name>, libc-alpha@...rceware.org, musl@...ts.openwall.com,
ardb@...nel.org, linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [GIT PULL] asm-generic changes for 5.19
On Sun, May 29, 2022 at 3:21 PM Marc Zyngier <maz@...nel.org> wrote:
> > My feeling is that there is also no point in merging a port without
> > the drivers as it cannot work on any hardware. On the other hand,
> > the libc submissions (glibc and musl) are currently blocked while
> > they are waiting for the kernel port to get merged.
>
> 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).
Ok, thanks for taking another look. I think we should just merge the
port without the drivers then, and you can make a decision on
the irqchip drivers after you've reviewed the latest version.
Arnd
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
