From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-2.3] fw_cfg-test: Fix test path to include architecture
Date: Thu, 19 Mar 2015 18:54:02 +0100 [thread overview]
Message-ID: <550B0D3A.7000903@suse.de> (raw)
In-Reply-To: <1426787272-17921-1-git-send-email-afaerber@suse.de>
Am 19.03.2015 um 18:47 schrieb Andreas Färber:
> Use qtest_add_func() instead of g_test_add_func() to reflect
> the architecture tested, changing GTester paths as follows:
>
> /fw_cfg/foo -> /x86_64/fw_cfg/foo etc.
>
Actually this should even be
Cc: qemu-stable@nongnu.org
It's been wrong since the beginning.
Andreas
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> tests/fw_cfg-test.c | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/tests/fw_cfg-test.c b/tests/fw_cfg-test.c
> index 5c8f8d6..9be78e9 100644
> --- a/tests/fw_cfg-test.c
> +++ b/tests/fw_cfg-test.c
> @@ -109,21 +109,21 @@ int main(int argc, char **argv)
>
> fw_cfg = pc_fw_cfg_init();
>
> - g_test_add_func("/fw_cfg/signature", test_fw_cfg_signature);
> - g_test_add_func("/fw_cfg/id", test_fw_cfg_id);
> - g_test_add_func("/fw_cfg/uuid", test_fw_cfg_uuid);
> - g_test_add_func("/fw_cfg/ram_size", test_fw_cfg_ram_size);
> - g_test_add_func("/fw_cfg/nographic", test_fw_cfg_nographic);
> - g_test_add_func("/fw_cfg/nb_cpus", test_fw_cfg_nb_cpus);
> + qtest_add_func("fw_cfg/signature", test_fw_cfg_signature);
> + qtest_add_func("fw_cfg/id", test_fw_cfg_id);
> + qtest_add_func("fw_cfg/uuid", test_fw_cfg_uuid);
> + qtest_add_func("fw_cfg/ram_size", test_fw_cfg_ram_size);
> + qtest_add_func("fw_cfg/nographic", test_fw_cfg_nographic);
> + qtest_add_func("fw_cfg/nb_cpus", test_fw_cfg_nb_cpus);
> #if 0
> - g_test_add_func("/fw_cfg/machine_id", test_fw_cfg_machine_id);
> - g_test_add_func("/fw_cfg/kernel", test_fw_cfg_kernel);
> - g_test_add_func("/fw_cfg/initrd", test_fw_cfg_initrd);
> - g_test_add_func("/fw_cfg/boot_device", test_fw_cfg_boot_device);
> + qtest_add_func("fw_cfg/machine_id", test_fw_cfg_machine_id);
> + qtest_add_func("fw_cfg/kernel", test_fw_cfg_kernel);
> + qtest_add_func("fw_cfg/initrd", test_fw_cfg_initrd);
> + qtest_add_func("fw_cfg/boot_device", test_fw_cfg_boot_device);
> #endif
> - g_test_add_func("/fw_cfg/max_cpus", test_fw_cfg_max_cpus);
> - g_test_add_func("/fw_cfg/numa", test_fw_cfg_numa);
> - g_test_add_func("/fw_cfg/boot_menu", test_fw_cfg_boot_menu);
> + qtest_add_func("fw_cfg/max_cpus", test_fw_cfg_max_cpus);
> + qtest_add_func("fw_cfg/numa", test_fw_cfg_numa);
> + qtest_add_func("fw_cfg/boot_menu", test_fw_cfg_boot_menu);
>
> cmdline = g_strdup_printf("-uuid 4600cb32-38ec-4b2f-8acb-81c6ea54f2d8 ");
> s = qtest_start(cmdline);
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-03-19 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:47 [Qemu-devel] [PATCH for-2.3] fw_cfg-test: Fix test path to include architecture Andreas Färber
2015-03-19 17:54 ` Andreas Färber [this message]
2015-03-21 15:36 ` Paolo Bonzini
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=550B0D3A.7000903@suse.de \
--to=afaerber@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.