qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: lvivier@redhat.com, thuth@redhat.com, alxndr@bu.edu,
	bsd@redhat.com, stefanha@redhat.com, pbonzini@redhat.com
Subject: [PATCH 0/3] fuzz: Probably there is a better way to do this
Date: Fri, 24 Apr 2020 09:11:39 +0200	[thread overview]
Message-ID: <20200424071142.3525-1-armbru@redhat.com> (raw)

... the comment next to qos_set_machines_devices_available() wonders.
Yup, there is!

Markus Armbruster (3):
  Makefile: Drop unused, broken target recurse-fuzz
  fuzz: Simplify how we compute available machines and types
  libqos: Give get_machine_allocator() internal linkage

 Makefile                          |  1 -
 tests/qtest/libqos/qos_external.h | 10 +++--
 tests/qtest/fuzz/qos_fuzz.c       | 34 ++++-----------
 tests/qtest/libqos/qos_external.c | 72 +++++++++++--------------------
 tests/qtest/qos-test.c            | 29 +++++++++----
 5 files changed, 60 insertions(+), 86 deletions(-)

-- 
2.21.1



             reply	other threads:[~2020-04-24  7:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  7:11 Markus Armbruster [this message]
2020-04-24  7:11 ` [PATCH 1/3] Makefile: Drop unused, broken target recurse-fuzz Markus Armbruster
2020-04-24 15:41   ` Alexander Bulekov
2020-04-24  7:11 ` [PATCH 2/3] fuzz: Simplify how we compute available machines and types Markus Armbruster
2020-04-24  8:31   ` Philippe Mathieu-Daudé
2020-04-24 15:41   ` Alexander Bulekov
2020-04-24  7:11 ` [PATCH 3/3] libqos: Give get_machine_allocator() internal linkage Markus Armbruster
2020-04-24  8:24   ` Philippe Mathieu-Daudé
2020-04-29  7:15 ` [PATCH 0/3] fuzz: Probably there is a better way to do this Markus Armbruster

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=20200424071142.3525-1-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=alxndr@bu.edu \
    --cc=bsd@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).