qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, qemu-stable@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.3 v2 3/4] i440fx-test: Fix test paths to include architecture
Date: Wed, 25 Mar 2015 18:14:02 -0400	[thread overview]
Message-ID: <5513332A.7030705@redhat.com> (raw)
In-Reply-To: <1427307623-2425-4-git-send-email-afaerber@suse.de>



On 03/25/2015 02:20 PM, Andreas Färber wrote:
> Replace g_test_add_func() with new qtest_add_func() and g_test_add()
> macro with qtest_add() macro.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
>   tests/i440fx-test.c | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/tests/i440fx-test.c b/tests/i440fx-test.c
> index a3f7279..d0bc8de 100644
> --- a/tests/i440fx-test.c
> +++ b/tests/i440fx-test.c
> @@ -383,8 +383,8 @@ static void add_firmware_test(const char *testpath,
>                                 void (*setup_fixture)(FirmwareTestFixture *f,
>                                                       gconstpointer test_data))
>   {
> -    g_test_add(testpath, FirmwareTestFixture, NULL, setup_fixture,
> -               test_i440fx_firmware, NULL);
> +    qtest_add(testpath, FirmwareTestFixture, NULL, setup_fixture,
> +              test_i440fx_firmware, NULL);
>   }
>
>   static void request_bios(FirmwareTestFixture *fixture,
> @@ -408,10 +408,10 @@ int main(int argc, char **argv)
>
>       data.num_cpus = 1;
>
> -    g_test_add_data_func("/i440fx/defaults", &data, test_i440fx_defaults);
> -    g_test_add_data_func("/i440fx/pam", &data, test_i440fx_pam);
> -    add_firmware_test("/i440fx/firmware/bios", request_bios);
> -    add_firmware_test("/i440fx/firmware/pflash", request_pflash);
> +    qtest_add_data_func("i440fx/defaults", &data, test_i440fx_defaults);
> +    qtest_add_data_func("i440fx/pam", &data, test_i440fx_pam);
> +    add_firmware_test("i440fx/firmware/bios", request_bios);
> +    add_firmware_test("i440fx/firmware/pflash", request_pflash);
>
>       ret = g_test_run();
>       return ret;
>

Reviewed-by: John Snow <jsnow@redhat.com>

  reply	other threads:[~2015-03-25 22:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 18:20 [Qemu-devel] [PATCH for-2.3 v2 0/4] qtest: Fix remaining test paths to include architecture Andreas Färber
2015-03-25 18:20 ` [Qemu-devel] [PATCH for-2.3 v2 1/4] qtest: Add qtest_add_data_func() wrapper function Andreas Färber
2015-03-25 18:20 ` [Qemu-devel] [PATCH for-2.3 v2 2/4] qtest: Add qtest_add() wrapper macro Andreas Färber
2015-03-25 22:13   ` John Snow
2015-03-25 18:20 ` [Qemu-devel] [PATCH for-2.3 v2 3/4] i440fx-test: Fix test paths to include architecture Andreas Färber
2015-03-25 22:14   ` John Snow [this message]
2015-03-25 18:20 ` [Qemu-devel] [PATCH v2 4/4] tests: Use qtest_add_data_func() consistently Andreas Färber
2015-03-25 22:14   ` John Snow
2015-03-26 15:41     ` Andreas Färber
2015-03-27 18:46       ` John Snow
2015-05-19 12:35         ` Andreas Färber
2015-05-19 15:38           ` John Snow

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=5513332A.7030705@redhat.com \
    --to=jsnow@redhat.com \
    --cc=afaerber@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@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).