From: Hanna Reitz <hreitz@redhat.com>
To: laokz <laokz@foxmail.com>, qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: kwolf@redhat.com
Subject: Re: [PATCH] tests: add (riscv virt) machine mapping to testenv
Date: Mon, 7 Mar 2022 18:04:28 +0100 [thread overview]
Message-ID: <35ea2e99-8049-9b72-b639-744afcdde726@redhat.com> (raw)
In-Reply-To: <tencent_451EA141786954DB4F7E4D7D4F9334EE1106@qq.com>
On 07.03.22 15:13, laokz wrote:
> Some qemu-iotests(040 etc) use PCI disk to do test. Without the
> mapping, RISC-V flavor use spike as default machine which has no
> PCI bus, causing test failure.
>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/894
>
> Signed-off-by: laokz <laokz@foxmail.com>
Hi!
Thank you for this quick patch, it looks good to me! I can reproduce
the problem you reported, and this patch does resolve it.
There might be one problem, though, and that’s the Signed-off-by tag.
The qemu project requires it to be formatted like the Linux kernel does,
and so our docs/devel/submitting-a-patch.rst file links to
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=f6f94e2ab1b33f0082ac22d71f66385a60d8157f#n297
. Like the kernel, we thus require a real name to appear in the S-o-b.
I’m used to seeing names written with a capital letter, and personal
names consisting just of a single name are rare, so that’s why I have to
ask you – is laokz your real name, i.e. not a pseudonym? If you say it
is, that’ll be fine for me.
If it isn’t and you don’t wish to disclose your real name, that will be
a bit of a problem legally, but I think in this case the patch is simple
enough that we can probably find a way around it.
Hanna
> ---
> tests/qemu-iotests/testenv.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/qemu-iotests/testenv.py b/tests/qemu-iotests/testenv.py
> index 0f32897fe8..975f26a785 100644
> --- a/tests/qemu-iotests/testenv.py
> +++ b/tests/qemu-iotests/testenv.py
> @@ -238,6 +238,8 @@ def __init__(self, imgfmt: str, imgproto: str, aiomode: str,
> ('aarch64', 'virt'),
> ('avr', 'mega2560'),
> ('m68k', 'virt'),
> + ('riscv32', 'virt'),
> + ('riscv64', 'virt'),
> ('rx', 'gdbsim-r5f562n8'),
> ('tricore', 'tricore_testboard')
> )
next prev parent reply other threads:[~2022-03-07 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 14:13 [PATCH] tests: add (riscv virt) machine mapping to testenv laokz
2022-03-07 17:04 ` Hanna Reitz [this message]
2022-03-08 4:33 ` [PATCH v2] " laokz
2022-03-08 6:40 ` Alistair Francis
2022-03-09 14:56 ` Hanna Reitz
2022-03-10 6:05 ` laokz
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=35ea2e99-8049-9b72-b639-744afcdde726@redhat.com \
--to=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=laokz@foxmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
/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).