From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, mprivozn@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] vl: Fix -drive / -blockdev persistent reservation management
Date: Tue, 4 Jun 2019 17:12:49 +0200 [thread overview]
Message-ID: <20190604151251.9903-1-armbru@redhat.com> (raw)
This is a minimal regression fix. There's more work to do nearby.
Left for another day.
Markus Armbruster (2):
vl: Fix -drive / -blockdev persistent reservation management
vl: Document why objects are delayed
vl.c | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-04 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 15:12 Markus Armbruster [this message]
2019-06-04 15:12 ` [Qemu-devel] [PATCH 1/2] vl: Fix -drive / -blockdev persistent reservation management Markus Armbruster
2019-06-04 15:12 ` [Qemu-devel] [PATCH 2/2] vl: Document why objects are delayed Markus Armbruster
2019-06-04 15:22 ` [Qemu-devel] [PATCH 0/2] vl: Fix -drive / -blockdev persistent reservation management Michal Privoznik
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=20190604151251.9903-1-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).