From: Huacai Chen <chenhuacai@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Arnd Bergmann <arnd@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, musl@lists.openwall.com,
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: [musl] Re: [GIT PULL] asm-generic changes for 5.19
Date: Mon, 30 May 2022 14:28:09 +0800 [thread overview]
Message-ID: <CAAhV-H4icDqABQiT4ckKdsmfVzqBKjxncDt9649c2ijOD093gw@mail.gmail.com> (raw)
In-Reply-To: <875ylomq3m.wl-maz@kernel.org>
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:
> >
> > On Thu, May 26, 2022 at 5:00 PM Arnd Bergmann <arnd@kernel.org> wrote:
> > > - A series to add a generic ticket spinlock that can be shared by most
> > > architectures with a working cmpxchg or ll/sc type atomic, including
> > > the conversion of riscv, csky and openrisc. This series is also a
> > > prerequisite for the loongarch64 architecture port that will come as
> > > a separate pull request.
> >
> > An update on Loongarch: I was originally planning to send Linus a
> > pull request with
> > the branch with the contents from
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/log/?h=loongarch-next
> >
> > but I saw that this includes both the architecture code and some
> > device drivers (irqchip, pci, acpi) that are essential for the
> > kernel to actually boot. At least the irqchip driver has not passed
> > review because it uses a nonstandard way to integrate into ACPI, and
> > the PCI stuff may or may not be ready but has no Reviewed-by or
> > Acked-by tags from the maintainers. I clearly don't want to bypass
> > the subsystem maintainers on those drivers by sending a pull request
> > for the current branch.
>
> It seems that there is now a new contributor on the irqchip front, and
> the current approach *should* be better than the "copy MIPS and run"
> approach that was previously taken. I'm still to find time to review
> the new series (I just came back from a week off), but hopefully next
> week.
>
> > 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).
(adding linux-pci and linux-acpi maintainers to Cc)
Hi Bjorn and Rafael,
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.
Specifically:
I'd like to confirm with Bjorn, if the PCI patches are in a reasonable
shape and can get an Acked-by.
And Rafael: would you sync with the ACPICA repos to bring in the
LoongArch changes upstreamed there?
[1]: https://lore.kernel.org/linux-pci/20220430084846.3127041-1-chenhuacai@loongson.cn/T/#t
[2]: https://lore.kernel.org/linux-acpi/20220306111838.810959-1-chenhuacai@loongson.cn/T/#t
Thanks,
Huacai
>
> Thanks,
>
> M.
>
> --
> Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-05-30 6:28 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 [this message]
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-H4icDqABQiT4ckKdsmfVzqBKjxncDt9649c2ijOD093gw@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@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).