All of lore.kernel.org
 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, stefanha@redhat.com,
	qemu-block <qemu-block@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2 4/4] tests: Use qtest_add_data_func() consistently
Date: Fri, 27 Mar 2015 14:46:15 -0400	[thread overview]
Message-ID: <5515A577.2090008@redhat.com> (raw)
In-Reply-To: <551428A3.6090408@suse.de>



On 03/26/2015 11:41 AM, Andreas Färber wrote:
> Am 25.03.2015 um 23:14 schrieb John Snow:
>> On 03/25/2015 02:20 PM, Andreas Färber wrote:
>>> Replace uses of g_test_add_data_func() for QTest test cases.
>>>
>>> It is still valid to use it for any non-QTest test cases,
>>> which are not run for multiple target binaries.
>>>
>>> Suggested-by: John Snow <jsnow@redhat.com>
>>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>>> ---
>>>    tests/ahci-test.c       |  9 ++-------
>>>    tests/e1000-test.c      |  4 ++--
>>>    tests/eepro100-test.c   |  5 ++---
>>>    tests/endianness-test.c | 18 +++++++++---------
>>>    tests/pc-cpu-test.c     | 13 ++++++-------
>>>    tests/qom-test.c        |  4 ++--
>>>    6 files changed, 23 insertions(+), 30 deletions(-)
> [...]
>> Seems fine to me. The time lost with the nested printfs during test
>> initialization is likely not worth crying over in the glorious name of
>> consistency.
>>
>> ((Biased.))
>>
>> Also, what happened to the subject of this mail? Are only patches 1-3
>> for-2.3?
>
> Yes, I tend to be conservative during the Hard Freeze and 4/4 is not
> fixing a bug or improving test coverage. I don't think it would harm,
> but I don't push for it. Opinions?
>

Playing it safe is totally fine by me, I was just curious.
My R-b stands.

Thank you,
--John

>> All the same:
>>
>> Reviewed-by: John Snow <jsnow@redhat.com>
>
> Thanks,
> Andreas
>

  reply	other threads:[~2015-03-27 18:46 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
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 [this message]
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=5515A577.2090008@redhat.com \
    --to=jsnow@redhat.com \
    --cc=afaerber@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@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 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.