From: caiyinyu <caiyinyu@loongson.cn>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Cc: xuchenghua@loongson.cn
Subject: Re: [PATCH v2 01/14] LoongArch: Update NEWS and README for the LoongArch port.
Date: Fri, 15 Apr 2022 09:28:14 +0800 [thread overview]
Message-ID: <a17c434d-583d-07a2-6009-90849c89835c@loongson.cn> (raw)
In-Reply-To: <a19f8df6-9c47-2767-e254-957cdffe86f0@linaro.org>
在 2022/1/4 下午9:30, Adhemerval Zanella 写道:
> On 31/12/2021 03:44, caiyinyu wrote:
>> ---
>> NEWS | 2 ++
>> README | 1 +
>> 2 files changed, 3 insertions(+)
>>
>> diff --git a/NEWS b/NEWS
>> index 4762bfcc4e..c78143cc67 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -9,6 +9,8 @@ Version 2.35
>>
>> Major new features:
>>
>> +* Add LoongArch Port. Loongson Ltd.
>> +
>> * Unicode 14.0.0 Support: Character encoding, character type info, and
>> transliteration tables are all updated to Unicode 14.0.0, using
>> generator scripts contributed by Mike FABIAN (Red Hat).
> Please follow other ports description, such the recent one for or1k [1],
> by adding the minimum binutils, gcc, and Linux version required along
> with the triple name and any other relevant information (32/64-bit,
> endianess, time_t, LFS support, etc).
>
> Also put the addition at the end of the list.
>
>> diff --git a/README b/README
>> index d0f0edb393..f0812d7a80 100644
>> --- a/README
>> +++ b/README
>> @@ -31,6 +31,7 @@ The GNU C Library supports these configurations for using Linux kernels:
>> i[4567]86-*-linux-gnu
>> x86_64-*-linux-gnu Can build either x86_64 or x32
>> ia64-*-linux-gnu
>> + loongarch64-*-linux-gnu
>> m68k-*-linux-gnu
>> microblaze*-*-linux-gnu
>> mips-*-linux-gnu
> [1]https://patchwork.sourceware.org/project/glibc/patch/20220104031414.2416928-14-shorne@gmail.com/
Fixed.
next prev parent reply other threads:[~2022-04-15 1:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 6:44 [PATCH v2 00/14] GLIBC LoongArch PATCHES caiyinyu
2021-12-31 6:44 ` [PATCH v2 01/14] LoongArch: Update NEWS and README for the LoongArch port caiyinyu
2022-01-04 13:30 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu [this message]
2021-12-31 6:44 ` [PATCH v2 02/14] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2021-12-31 6:44 ` [PATCH v2 03/14] LoongArch: Add relocations and ELF flags to elf.h caiyinyu
2021-12-31 6:44 ` [PATCH v2 04/14] LoongArch: ABI Implementation caiyinyu
2022-01-04 13:46 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 05/14] LoongArch: Thread-Local Storage Support caiyinyu
2022-01-04 14:01 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 06/14] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-01-04 14:05 ` Adhemerval Zanella
2022-01-04 20:31 ` Joseph Myers
2021-12-31 6:44 ` [PATCH v2 07/14] LoongArch: Atomic and Locking Routines caiyinyu
2022-01-04 14:09 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 08/14] LoongArch: Linux Syscall Interface caiyinyu
2022-01-04 14:20 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 09/14] LoongArch: Linux ABI caiyinyu
2021-12-31 17:37 ` Joseph Myers
2022-04-15 1:27 ` caiyinyu
2022-01-04 14:24 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 10/14] LoongArch: Linux Startup and Dynamic Loading Code caiyinyu
2022-01-04 14:27 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 11/14] LoongArch: Add ABI Lists caiyinyu
2021-12-31 17:43 ` Joseph Myers
2022-04-15 1:27 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 12/14] LoongArch: Build Infastructure caiyinyu
2022-01-04 14:33 ` Adhemerval Zanella
2021-12-31 6:44 ` [PATCH v2 13/14] LoongArch: Hard Float Support caiyinyu
2021-12-31 17:47 ` Joseph Myers
2022-04-15 1:27 ` caiyinyu
2021-12-31 6:44 ` [PATCH v2 14/14] LoongArch: Update build-many-glibcs.py for the LoongArch Port caiyinyu
2021-12-31 17:34 ` [PATCH v2 00/14] GLIBC LoongArch PATCHES Joseph Myers
2022-04-15 1:27 ` caiyinyu
2022-01-04 13:27 ` Adhemerval Zanella
2022-04-15 1:28 ` caiyinyu
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=a17c434d-583d-07a2-6009-90849c89835c@loongson.cn \
--to=caiyinyu@loongson.cn \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=xuchenghua@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).