From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
tanyuan@tinylab.org, thomas@t-8ch.de
Subject: Re: [PATCH v1 4/4] selftests/nolibc: add some notes about qemu tools
Date: Sun, 6 Aug 2023 12:12:41 +0200 [thread overview]
Message-ID: <20230806101241.GD10627@1wt.eu> (raw)
In-Reply-To: <6de680acbc2d87e13a680d4453ef022568bf489b.1691263493.git.falcon@tinylab.org>
On Sun, Aug 06, 2023 at 03:51:24AM +0800, Zhangjin Wu wrote:
> Almost all distributions provide qemu-system-$(XARCH), their firmwares
> and qemu-$(XARCH), but for the new riscv and loongarch, users may still
> need to download external firmwares or compile qemu from scratch, let's
> add some notes about them.
That's indeed useful information but I think that we should really move
all the download instructions to a separate file. I wanted to write one
anyway, but didn't have the time with all the build tests to run :-(
I may propose one to be merged late, possibly.
Willy
prev parent reply other threads:[~2023-08-06 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 19:36 [PATCH v1 0/4] selftests/nolibc: customize CROSS_COMPILE for all supported architectures Zhangjin Wu
2023-08-05 19:38 ` [PATCH v1 1/4] selftests/nolibc: allow use x86_64 toolchain for i386 Zhangjin Wu
2023-08-05 19:44 ` [PATCH v1 2/4] selftests/nolibc: customize CROSS_COMPILE for many architectures Zhangjin Wu
2023-08-05 19:49 ` [PATCH v1 3/4] selftests/nolibc: customize CROSS_COMPILE for loongarch Zhangjin Wu
2023-08-05 19:51 ` [PATCH v1 4/4] selftests/nolibc: add some notes about qemu tools Zhangjin Wu
2023-08-06 10:12 ` Willy Tarreau [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=20230806101241.GD10627@1wt.eu \
--to=w@1wt.eu \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tanyuan@tinylab.org \
--cc=thomas@t-8ch.de \
/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