From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, lvivier@redhat.com
Subject: [Qemu-devel] [PATCH for-2.9 0/2] Fix QemuOpts regression on bogus keys
Date: Mon, 20 Mar 2017 22:17:03 -0500 [thread overview]
Message-ID: <20170321031705.22291-1-eblake@redhat.com> (raw)
Reported to me off-list by Laurent Vivier, who found the
problem while working on https://bugzilla.redhat.com/1433193
Broken since 2.7, but the fix is a one-liner (pointing out my
embarrassing mistake of mis-converting a pre-decrement operator);
as a bug fix, it still qualifies for 2.9 in spite of hard freeze,
on the other hand, as the regression was not introduced in 2.9,
I also understand if it is postponed.
Eric Blake (2):
tests: Expose regression in QemuOpts visitor
qapi: Fix QemuOpts visitor regression on unvisited input
qapi/opts-visitor.c | 6 +++---
tests/test-opts-visitor.c | 29 ++++++++++++++++++++++++++---
2 files changed, 29 insertions(+), 6 deletions(-)
--
2.9.3
next reply other threads:[~2017-03-21 3:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 3:17 Eric Blake [this message]
2017-03-21 3:17 ` [Qemu-devel] [PATCH 1/2] tests: Expose regression in QemuOpts visitor Eric Blake
2017-03-21 4:41 ` Michael Roth
2017-03-21 9:01 ` Laurent Vivier
2017-03-21 13:21 ` Eric Blake
2017-03-21 13:33 ` Laurent Vivier
2017-03-21 15:36 ` Eric Blake
2017-03-21 16:01 ` Markus Armbruster
2017-03-21 16:10 ` Laurent Vivier
2017-03-21 3:17 ` [Qemu-devel] [PATCH 2/2] qapi: Fix QemuOpts visitor regression on unvisited input Eric Blake
2017-03-21 4:42 ` Michael Roth
2017-03-21 8:19 ` Laurent Vivier
2017-03-21 9:28 ` [Qemu-devel] [PATCH for-2.9 0/2] Fix QemuOpts regression on bogus keys Markus Armbruster
2017-03-21 13:23 ` Eric Blake
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=20170321031705.22291-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=lvivier@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).