From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Huacai Chen" <chenhuacai@loongson.cn>,
"Song Gao" <gaosong@loongson.cn>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Jiajie Chen" <c@jia.je>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH 0/4] target/loongarch: Cleanups in preparation of loongarch32 support
Date: Fri, 18 Aug 2023 12:34:21 +0200 [thread overview]
Message-ID: <20230818103425.16271-1-philmd@linaro.org> (raw)
Jiajie, this series contains few notes I took while
reviewing your series adding loongarch32 support [*].
If your series isn't merged, consider rebasing it on
this one.
Regards,
Phil.
[*] https://lore.kernel.org/qemu-devel/20230817093121.1053890-1-gaosong@loongson.cn/
Philippe Mathieu-Daudé (4):
target/loongarch: Log I/O write accesses to CSR registers
target/loongarch: Remove duplicated disas_set_info assignment
target/loongarch: Rename 64-bit specific functions
target/loongarch: Extract 64-bit specifics to
loongarch64_cpu_class_init
target/loongarch/cpu.c | 42 +++++++++++++++++++++++++-----------------
1 file changed, 25 insertions(+), 17 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-18 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 10:34 Philippe Mathieu-Daudé [this message]
2023-08-18 10:34 ` [PATCH 1/4] target/loongarch: Log I/O write accesses to CSR registers Philippe Mathieu-Daudé
2023-08-18 10:34 ` [PATCH 2/4] target/loongarch: Remove duplicated disas_set_info assignment Philippe Mathieu-Daudé
2023-08-18 15:58 ` Richard Henderson
2023-08-18 10:34 ` [PATCH 3/4] target/loongarch: Rename 64-bit specific functions Philippe Mathieu-Daudé
2023-08-18 15:59 ` Richard Henderson
2023-08-18 10:34 ` [PATCH 4/4] target/loongarch: Extract 64-bit specifics to loongarch64_cpu_class_init Philippe Mathieu-Daudé
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=20230818103425.16271-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=c@jia.je \
--cc=chenhuacai@loongson.cn \
--cc=gaosong@loongson.cn \
--cc=qemu-devel@nongnu.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).