From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH for-5.2 3/4] qtest: escape device name in device-introspect-test
Date: Fri, 06 Nov 2020 14:15:40 +0100 [thread overview]
Message-ID: <87zh3uiq2r.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20201103151452.416784-4-pbonzini@redhat.com> (Paolo Bonzini's message of "Tue, 3 Nov 2020 10:14:51 -0500")
Paolo Bonzini <pbonzini@redhat.com> writes:
> device-introspect-test uses HMP, so it should escape the device name
> properly. Because of this, a few devices that had commas in their
> names were escaping testing.
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
$ git-grep '\.name *= *"[^"]*,' | cat
hw/block/fdc.c: .name = "SUNW,fdtwo"
Any others?
next prev parent reply other threads:[~2020-11-06 13:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 15:14 [PATCH for-5.2 0/4] deprecate short-form boolean options Paolo Bonzini
2020-11-03 15:14 ` [PATCH for-5.2 1/4] ivshmem-test: do not use short-form boolean option Paolo Bonzini
2020-11-04 7:40 ` Thomas Huth
2020-11-04 9:12 ` Markus Armbruster
2020-11-03 15:14 ` [PATCH for-5.2 2/4] qemu-option: move help handling to get_opt_name_value Paolo Bonzini
2020-11-04 12:21 ` Markus Armbruster
2020-11-04 12:49 ` Paolo Bonzini
2020-11-03 15:14 ` [PATCH for-5.2 3/4] qtest: escape device name in device-introspect-test Paolo Bonzini
2020-11-04 7:44 ` Thomas Huth
2020-11-04 8:10 ` Paolo Bonzini
2020-11-06 13:15 ` Markus Armbruster [this message]
2020-11-06 13:23 ` Paolo Bonzini
2020-11-06 15:34 ` Markus Armbruster
2020-11-03 15:14 ` [PATCH for-5.2 4/4] qemu-option: warn for short-form boolean options Paolo Bonzini
2020-11-03 16:08 ` Daniel P. Berrangé
2020-11-03 16:18 ` Paolo Bonzini
2020-11-04 13:43 ` Markus Armbruster
2020-11-03 21:22 ` Igor Mammedov
2020-11-03 21:41 ` Paolo Bonzini
2020-11-04 11:04 ` Igor Mammedov
2020-11-03 15:33 ` [PATCH for-5.2 0/4] deprecate " no-reply
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=87zh3uiq2r.fsf@dusky.pond.sub.org \
--to=armbru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.