From: Thomas Huth <thuth@redhat.com>
To: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [PULL 4/9] tests/qtest/fuzz: Add missing spaces in description
Date: Mon, 13 Jul 2020 12:55:29 +0200 [thread overview]
Message-ID: <20200713105534.10872-5-thuth@redhat.com> (raw)
In-Reply-To: <20200713105534.10872-1-thuth@redhat.com>
There should be a space between "forking" and "for".
Message-Id: <20200709083719.22221-1-thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
tests/qtest/fuzz/virtio_scsi_fuzz.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/qtest/fuzz/virtio_scsi_fuzz.c b/tests/qtest/fuzz/virtio_scsi_fuzz.c
index 51dce491ab..3a9ea13736 100644
--- a/tests/qtest/fuzz/virtio_scsi_fuzz.c
+++ b/tests/qtest/fuzz/virtio_scsi_fuzz.c
@@ -191,7 +191,7 @@ static void register_virtio_scsi_fuzz_targets(void)
{
fuzz_add_qos_target(&(FuzzTarget){
.name = "virtio-scsi-fuzz",
- .description = "Fuzz the virtio-scsi virtual queues, forking"
+ .description = "Fuzz the virtio-scsi virtual queues, forking "
"for each fuzz run",
.pre_vm_init = &counter_shm_init,
.pre_fuzz = &virtio_scsi_pre_fuzz,
@@ -202,7 +202,7 @@ static void register_virtio_scsi_fuzz_targets(void)
fuzz_add_qos_target(&(FuzzTarget){
.name = "virtio-scsi-flags-fuzz",
- .description = "Fuzz the virtio-scsi virtual queues, forking"
+ .description = "Fuzz the virtio-scsi virtual queues, forking "
"for each fuzz run (also fuzzes the virtio flags)",
.pre_vm_init = &counter_shm_init,
.pre_fuzz = &virtio_scsi_pre_fuzz,
--
2.18.1
next prev parent reply other threads:[~2020-07-13 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 10:55 [PULL 0/9] Fuzzer, configure, gitlab and misc patches Thomas Huth
2020-07-13 10:55 ` [PULL 1/9] configure: fix malloc check Thomas Huth
2020-07-13 10:55 ` [PULL 2/9] configure: do not clobber CFLAGS with --enable-fuzzing Thomas Huth
2020-07-13 10:55 ` [PULL 3/9] fuzz: add missing header for rcu_enable_atfork Thomas Huth
2020-07-13 10:55 ` Thomas Huth [this message]
2020-07-13 10:55 ` [PULL 5/9] docs/devel/fuzzing: Fix bugs in documentation Thomas Huth
2020-07-13 10:55 ` [PULL 6/9] Remove the CONFIG_PRAGMA_DIAGNOSTIC_AVAILABLE switch Thomas Huth
2020-07-13 10:55 ` [PULL 7/9] disas/sh4: Add missing fallthrough annotations Thomas Huth
2020-07-13 10:55 ` [PULL 8/9] GitLab Gating CI: introduce pipeline-status contrib script Thomas Huth
2020-07-13 10:55 ` [PULL 9/9] docs/system/s390x: Improve the 3270 documentation Thomas Huth
2020-07-13 11:27 ` [PULL 0/9] Fuzzer, configure, gitlab and misc patches no-reply
2020-07-13 13:35 ` Peter Maydell
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=20200713105534.10872-5-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--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).