From: WANG Xuerui <i.qemu@xen0n.name>
To: Song Gao <gaosong@loongson.cn>, qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org, laurent@vivier.eu,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH v15 1/9] linux-user: Add LoongArch generic header files
Date: Thu, 9 Jun 2022 17:54:02 +0800 [thread overview]
Message-ID: <6df7787c-5625-93b3-fcb0-ed0b76e551b1@xen0n.name> (raw)
In-Reply-To: <20220609024209.2406188-2-gaosong@loongson.cn>
On 2022/6/9 10:42, Song Gao wrote:
> This includes:
> - sockbits.h
> - target_errno_defs.h
> - target_fcntl.h
> - termbits.h
> - target_resource.h
> - target_structs.h
>
> Signed-off-by: Song Gao <gaosong@loongson.cn>
> Signed-off-by: Xiaojuan Yang <yangxiaojuan@loongson.cn>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> linux-user/loongarch64/sockbits.h | 11 +++++++++++
> linux-user/loongarch64/target_errno_defs.h | 12 ++++++++++++
> linux-user/loongarch64/target_fcntl.h | 11 +++++++++++
> linux-user/loongarch64/target_prctl.h | 1 +
> linux-user/loongarch64/target_resource.h | 11 +++++++++++
> linux-user/loongarch64/target_structs.h | 11 +++++++++++
> linux-user/loongarch64/termbits.h | 11 +++++++++++
> 7 files changed, 68 insertions(+)
> create mode 100644 linux-user/loongarch64/sockbits.h
> create mode 100644 linux-user/loongarch64/target_errno_defs.h
> create mode 100644 linux-user/loongarch64/target_fcntl.h
> create mode 100644 linux-user/loongarch64/target_prctl.h
> create mode 100644 linux-user/loongarch64/target_resource.h
> create mode 100644 linux-user/loongarch64/target_structs.h
> create mode 100644 linux-user/loongarch64/termbits.h
So this is all nicely generic.
Reviewed-by: WANG Xuerui <git@xen0n.name>
next prev parent reply other threads:[~2022-06-09 12:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 2:42 [PATCH v15 0/9] Add LoongArch linux-user emulation support Song Gao
2022-06-09 2:42 ` [PATCH v15 1/9] linux-user: Add LoongArch generic header files Song Gao
2022-06-09 9:54 ` WANG Xuerui [this message]
2022-06-09 2:42 ` [PATCH v15 2/9] linux-user: Add LoongArch signal support Song Gao
2022-06-09 18:00 ` Richard Henderson
2022-06-09 2:42 ` [PATCH v15 3/9] linux-user: Add LoongArch elf support Song Gao
2022-06-09 2:42 ` [PATCH v15 4/9] linux-user: Add LoongArch syscall support Song Gao
2022-06-09 10:04 ` WANG Xuerui
2022-06-10 1:15 ` gaosong
2022-06-09 2:42 ` [PATCH v15 5/9] linux-user: Add LoongArch cpu_loop support Song Gao
2022-06-09 2:42 ` [PATCH v15 6/9] default-configs: Add loongarch linux-user support Song Gao
2022-06-09 10:11 ` WANG Xuerui
2022-06-09 18:14 ` Richard Henderson
2022-06-09 2:42 ` [PATCH v15 7/9] scripts: add loongarch64 binfmt config Song Gao
2022-06-09 2:42 ` [PATCH v15 8/9] target/loongarch: Adjust functions and structure to support user-mode Song Gao
2022-06-09 10:18 ` WANG Xuerui
2022-06-09 18:42 ` Richard Henderson
2022-06-10 6:53 ` gaosong
2022-06-10 22:45 ` Richard Henderson
2022-06-11 3:10 ` gaosong
2022-06-11 16:06 ` Richard Henderson
2022-06-13 3:50 ` gaosong
2022-06-13 16:05 ` Richard Henderson
2022-06-09 2:42 ` [PATCH v15 9/9] target/loongarch: Update README Song Gao
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=6df7787c-5625-93b3-fcb0-ed0b76e551b1@xen0n.name \
--to=i.qemu@xen0n.name \
--cc=f4bug@amsat.org \
--cc=gaosong@loongson.cn \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=yangxiaojuan@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 NNTP newsgroup(s).