From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Jia Liu <proljc@gmail.com>,
Stafford Horne <shorne@gmail.com>
Cc: qemu-trivial@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [PATCH] system: Enable the device aliases for or1k, too
Date: Fri, 5 Jul 2024 14:46:07 +0200 [thread overview]
Message-ID: <b822017b-bd83-4cf1-8ecb-22d998b1b99a@linaro.org> (raw)
In-Reply-To: <73a0498e-8f66-46ff-a4f2-fcb6b80f9d42@linaro.org>
On 5/7/24 14:39, Philippe Mathieu-Daudé wrote:
> On 5/7/24 11:08, Thomas Huth wrote:
>> Now that we've got a "virt" machine for or1k that supports PCI, too,
>> we can also enable the virtio device aliases like we do on other
>> similar platforms. This will e.g. help to run the iotests with
>> qemu-system-or1k later.
>
> Indeed, since 2022 in commit 40fef82c4e ("hw/openrisc:
> Add PCI bus support to virt").
>
>>
>> While we're at it, sort QEMU_ARCH_LOONGARCH alphabetically into
>> the list.
>
> Suggestion: a preliminary patch sorting 1 arch per line ;)
Done here:
https://lore.kernel.org/qemu-devel/20240705124528.97471-1-philmd@linaro.org/
>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> system/qdev-monitor.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>
prev parent reply other threads:[~2024-07-05 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 9:08 [PATCH] system: Enable the device aliases for or1k, too Thomas Huth
2024-07-05 12:39 ` Philippe Mathieu-Daudé
2024-07-05 12:46 ` 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=b822017b-bd83-4cf1-8ecb-22d998b1b99a@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=proljc@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=shorne@gmail.com \
--cc=thuth@redhat.com \
/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).