From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Zhiguo Wu" <wuzhiguo@loongson.cn>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Bibo Mao" <maobibo@loongson.cn>,
"Song Gao" <gaosong@loongson.cn>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Beraldo Leal" <bleal@redhat.com>, "WANG Xuerui" <git@xen0n.name>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Xianglai Li" <lixianglai@loongson.cn>,
"Tianrui Zhao" <zhaotianrui@loongson.cn>
Subject: Re: [NOTFORMERGE PATCH 2/2] gitlab: Add Loongarch64 KVM-only build
Date: Thu, 11 Jan 2024 10:26:33 +0100 [thread overview]
Message-ID: <fabe07d9-dde1-47f9-8beb-3c5c7b97f88f@linaro.org> (raw)
In-Reply-To: <dbc7f2c6-15c0-4d5a-abf7-8946ff2d03cb@redhat.com>
On 11/1/24 08:10, Thomas Huth wrote:
> On 02/01/2024 18.22, Philippe Mathieu-Daudé wrote:
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> Used to test
>> https://lore.kernel.org/qemu-devel/20231228084051.3235354-1-zhaotianrui@loongson.cn/
>
> So why is it NOTFORMERGE ? Don't we want to test KVM-only builds for
> loongarch in the long run?
We do. I was just waiting the loongarch64/KVM support was first.
prev parent reply other threads:[~2024-01-11 9:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 17:22 [PATCH 0/2] gitlab: Add config for Loongarch64 custom runner Philippe Mathieu-Daudé
2024-01-02 17:22 ` [PATCH 1/2] gitlab: Introduce Loongarch64 runner Philippe Mathieu-Daudé
2024-01-11 7:08 ` Thomas Huth
2024-01-11 7:25 ` gaosong
2024-01-11 8:26 ` Thomas Huth
2024-01-11 12:05 ` gaosong
2024-01-11 13:11 ` Philippe Mathieu-Daudé
2024-01-12 9:52 ` gaosong
2024-01-15 10:08 ` gaosong
2024-01-02 17:22 ` [NOTFORMERGE PATCH 2/2] gitlab: Add Loongarch64 KVM-only build Philippe Mathieu-Daudé
2024-01-11 7:10 ` Thomas Huth
2024-01-11 7:37 ` gaosong
2024-01-11 8:20 ` Thomas Huth
2024-01-11 8:50 ` gaosong
2024-01-11 9:04 ` Thomas Huth
2024-01-11 9:51 ` gaosong
2024-01-11 11:26 ` Philippe Mathieu-Daudé
2024-01-11 11:41 ` gaosong
2024-01-24 8:56 ` gaosong
2024-01-11 9:26 ` Philippe Mathieu-Daudé [this message]
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=fabe07d9-dde1-47f9-8beb-3c5c7b97f88f@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=gaosong@loongson.cn \
--cc=git@xen0n.name \
--cc=lixianglai@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wuzhiguo@loongson.cn \
--cc=yangxiaojuan@loongson.cn \
--cc=zhaotianrui@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).