From: Thomas Huth <thuth@redhat.com>
To: Michael Labiuk <michael.labiuk@virtuozzo.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
den@virtuozzo.com
Subject: Re: [PATCH v5 7/9] tests/x86: replace snprint() by g_strdup_printf() in drive_del-test
Date: Tue, 11 Oct 2022 13:27:53 +0200 [thread overview]
Message-ID: <2280c594-2ae1-bc42-d9d4-7f3598725564@redhat.com> (raw)
In-Reply-To: <20220929223547.1429580-8-michael.labiuk@virtuozzo.com>
On 30/09/2022 00.35, Michael Labiuk via wrote:
> Using g_autofree char* and g_strdup_printf(...) instead of ugly
> snprintf on stack array.
>
> Signed-off-by: Michael Labiuk <michael.labiuk@virtuozzo.com>
> ---
> tests/qtest/drive_del-test.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/tests/qtest/drive_del-test.c b/tests/qtest/drive_del-test.c
> index 44b9578801..106c613f4f 100644
> --- a/tests/qtest/drive_del-test.c
> +++ b/tests/qtest/drive_del-test.c
> @@ -123,12 +123,10 @@ static const char *qvirtio_get_dev_type(void)
>
> static void device_add(QTestState *qts)
> {
> - QDict *response;
> - char driver[32];
> - snprintf(driver, sizeof(driver), "virtio-blk-%s",
> - qvirtio_get_dev_type());
> -
> - response = qtest_qmp(qts, "{'execute': 'device_add',"
> + g_autofree char *driver = g_strdup_printf("virtio-blk-%s",
> + qvirtio_get_dev_type());
> + QDict *response =
> + qtest_qmp(qts, "{'execute': 'device_add',"
> " 'arguments': {"
> " 'driver': %s,"
> " 'drive': 'drive0',"
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2022-10-11 13:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 22:35 [PATCH v5 0/9] Add 'q35' machine type to hotplug tests Michael Labiuk via
2022-09-29 22:35 ` [PATCH v5 1/9] tests/x86: add helper qtest_qmp_device_del_send() Michael Labiuk via
2022-10-11 10:59 ` Thomas Huth
2022-09-29 22:35 ` [PATCH v5 2/9] tests/x86: Add subtest with 'q35' machine type to device-plug-test Michael Labiuk via
2022-10-11 11:10 ` Thomas Huth
2022-09-29 22:35 ` [PATCH v5 3/9] tests/x86: Refactor hot unplug hd-geo-test Michael Labiuk via
2022-10-11 11:18 ` Thomas Huth
2022-09-29 22:35 ` [PATCH v5 4/9] tests/x86: Add 'q35' machine type to override-tests in hd-geo-test Michael Labiuk via
2022-10-11 11:23 ` Thomas Huth
2022-09-29 22:35 ` [PATCH v5 5/9] tests/x86: Add 'q35' machine type to hotplug hd-geo-test Michael Labiuk via
2022-10-11 11:24 ` Thomas Huth
2022-09-29 22:35 ` [PATCH v5 6/9] tests/x86: Fix comment typo in drive_del-test Michael Labiuk via
2022-10-11 11:25 ` Thomas Huth
2022-09-29 22:35 ` [PATCH v5 7/9] tests/x86: replace snprint() by g_strdup_printf() " Michael Labiuk via
2022-10-11 11:27 ` Thomas Huth [this message]
2022-10-18 6:39 ` Philippe Mathieu-Daudé
2022-09-29 22:35 ` [PATCH v5 8/9] tests/x86: Add 'q35' machine type to drive_del-test Michael Labiuk via
2022-10-11 11:44 ` Thomas Huth
2022-09-29 22:35 ` [PATCH v5 9/9] tests/x86: Add 'q35' machine type to ivshmem-test Michael Labiuk via
2022-10-11 11:54 ` Thomas Huth
2022-10-11 10:18 ` [PING PATCH v5] Add 'q35' machine type to hotplug tests Michael Labiuk
2022-10-11 12:09 ` Thomas Huth
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=2280c594-2ae1-bc42-d9d4-7f3598725564@redhat.com \
--to=thuth@redhat.com \
--cc=den@virtuozzo.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=michael.labiuk@virtuozzo.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).