On 5/30/22 21:01, Huacai Chen wrote:
Hi, Arnd,
On Mon, May 30, 2022 at 4:21 PM Arnd Bergmann <arnd@xxxxxxxxxx> wrote:
On Sun, May 29, 2022 at 3:10 PM WANG Xuerui <kernel@xxxxxxxxxx> 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.
Thanks for the recognition from both of you; it is my honor and pleasure
to contribute to the LoongArch port and to Linux in general.
As I'm still not entirely satisfied with my kernel development skills,
plus my day job is not kernel-related nor Loongson/LoongArch-related at
all, listing me as reviewer should be enough for now. I will take care
of the arch as long as I have the hardware.
BTW, there were already several breakages when rebasing the previous
revision (I believe it's commit 215da6d2dac0 ("MAINTAINERS: Add
maintainer information for LoongArch")) on top of linus' tree. Now I see
the loongarch-next HEAD is already rebased on top of what I believe to
be the current main branch, however I vaguely remember that it's not
good to base one's patches on top of "some random commit", so I wonder
whether the current branch state is appropriate for a PR?
