From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Zhiguo Wu" <wuzhiguo@loongson.cn>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Thomas Huth" <thuth@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>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Xianglai Li" <lixianglai@loongson.cn>,
"Tianrui Zhao" <zhaotianrui@loongson.cn>
Subject: [PATCH 0/2] gitlab: Add config for Loongarch64 custom runner
Date: Tue, 2 Jan 2024 18:22:37 +0100 [thread overview]
Message-ID: <20240102172239.69452-1-philmd@linaro.org> (raw)
Loongson Technology Corporation Limited offered to sponsor QEMU
with a Loongarch64 custom runner.
Philippe Mathieu-Daudé (2):
gitlab: Introduce Loongarch64 runner
gitlab: Add Loongarch64 KVM-only build
docs/devel/ci-jobs.rst.inc | 6 +++
.gitlab-ci.d/custom-runners.yml | 1 +
.../openeuler-22.03-loongarch64.yml | 43 +++++++++++++++++++
3 files changed, 50 insertions(+)
create mode 100644 .gitlab-ci.d/custom-runners/openeuler-22.03-loongarch64.yml
--
2.41.0
next reply other threads:[~2024-01-02 17:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 17:22 Philippe Mathieu-Daudé [this message]
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é
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=20240102172239.69452-1-philmd@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).