public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: caiyinyu <caiyinyu@loongson.cn>,
	WANG Xuerui <i.swmail@xen0n.name>,
	 adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
	 joseph_myers@mentor.com, carlos@redhat.com
Cc: liuzhensong@loongson.cn
Subject: Re: [PATCH v7 00/13] GLIBC LoongArch PATCHES
Date: Mon, 25 Jul 2022 16:28:05 +0800	[thread overview]
Message-ID: <c888d01be9e1d0ee666e2b20b6afc11e111eb25d.camel@xry111.site> (raw)
In-Reply-To: <6339e6bd-94a2-4d4a-069a-c332a48bd241@loongson.cn>

On Mon, 2022-07-25 at 16:21 +0800, caiyinyu wrote:
> Summary of test results:
>         1 FAIL
>      4576 PASS
>        22 UNSUPPORTED
>        12 XFAIL
>         6 XPASS
> Overall this is looking good. Thanks for your testing.
> 
> 
> So, is it necessary to release another version of v8??

I guess a v8 is better because the 17th patch (NEWS) needs a rebase
anyway.  But let's wait for Adhemerval's suggestion...

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2022-07-25  8:28 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  1:20 caiyinyu
2022-07-19  1:20 ` [PATCH v7 01/13] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2022-07-21 21:02   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 02/13] LoongArch: Add relocations and ELF flags to elf.h and scripts/glibcelf.py caiyinyu
2022-07-21 21:02   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 03/13] LoongArch: ABI Implementation caiyinyu
2022-07-20 12:29   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 04/13] LoongArch: Thread-Local Storage Support caiyinyu
2022-07-20 14:34   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 05/13] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-07-20 13:04   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 06/13] LoongArch: Atomic and Locking Routines caiyinyu
2022-07-20 14:32   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 07/13] LoongArch: Linux Syscall Interface caiyinyu
2022-07-20 14:35   ` Adhemerval Zanella Netto
2022-07-27  5:27   ` WANG Xuerui
2022-07-27  5:32     ` WANG Xuerui
2022-07-27 11:16       ` Adhemerval Zanella Netto
2022-07-27 13:01         ` WANG Xuerui
2022-07-27 19:22           ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 08/13] LoongArch: Linux ABI caiyinyu
2022-07-20 16:37   ` Adhemerval Zanella Netto
2022-07-20 17:19 ` [PATCH v7 00/13] GLIBC LoongArch PATCHES Adhemerval Zanella Netto
2022-07-21  2:44   ` caiyinyu
2022-07-24  9:49 ` WANG Xuerui
2022-07-24 11:51   ` Xi Ruoyao
2022-07-24 12:02     ` WANG Xuerui
2022-07-25  8:21       ` caiyinyu
2022-07-25  8:28         ` Xi Ruoyao [this message]
2022-07-25  1:58     ` 刘振松
2022-07-25  8:01       ` Xi Ruoyao
2022-07-25 13:27   ` Adhemerval Zanella Netto
2022-07-25 14:14     ` caiyinyu
2022-07-26 12:35       ` caiyinyu
2022-07-26 12:42         ` Adhemerval Zanella Netto
2022-07-26 14:00           ` Mark Wielaard

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=c888d01be9e1d0ee666e2b20b6afc11e111eb25d.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=adhemerval.zanella@linaro.org \
    --cc=caiyinyu@loongson.cn \
    --cc=carlos@redhat.com \
    --cc=i.swmail@xen0n.name \
    --cc=joseph_myers@mentor.com \
    --cc=libc-alpha@sourceware.org \
    --cc=liuzhensong@loongson.cn \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).