From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org
Cc: Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] hw/sparc/sun4m: Fix implicit creation of "-drive if=scsi" devices
Date: Thu, 8 Mar 2018 19:51:12 +0100 [thread overview]
Message-ID: <fe05591f-9f16-228c-7d8c-65eb04a941ab@redhat.com> (raw)
In-Reply-To: <2aa2df96-b1c3-deef-9fbf-a2560f58d17d@redhat.com>
On 08/03/2018 05:33, Thomas Huth wrote:
> Tested-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2018-03-08 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 9:39 [Qemu-devel] [PATCH] hw/sparc/sun4m: Fix implicit creation of "-drive if=scsi" devices Thomas Huth
2018-03-07 18:43 ` Mark Cave-Ayland
2018-03-08 4:33 ` Thomas Huth
2018-03-08 18:51 ` Paolo Bonzini [this message]
2018-03-08 18:57 ` Mark Cave-Ayland
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=fe05591f-9f16-228c-7d8c-65eb04a941ab@redhat.com \
--to=pbonzini@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--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).