From: Leandro Dorileo <l@dorileo.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Wenchao Xia" <wenchaoqemu@gmail.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Chunyan Liu" <cyliu@suse.com>,
qemu-devel@nongnu.org, "Anthony Liguori" <anthony@codemonkey.ws>,
"Luiz Capitulino" <lcapitulino@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3] QemuOpt: add unit tests
Date: Mon, 19 May 2014 18:31:02 -0300 [thread overview]
Message-ID: <20140519213102.GB2051@dorilex-lnv.MultilaserAP> (raw)
In-Reply-To: <8738gvp6fp.fsf@blackfin.pond.sub.org>
On Wed, Apr 30, 2014 at 10:28:26AM +0200, Markus Armbruster wrote:
> Leandro Dorileo <l@dorileo.org> writes:
>
> > Hi Andreas,
> >
> > On Mon, Apr 28, 2014 at 09:02:12PM +0200, Andreas Färber wrote:
> >> Am 28.04.2014 20:55, schrieb Leandro Dorileo:
> >> > ping?
> >> >
> >> >
> >> > On Tue, Mar 25, 2014 at 10:27:19AM -0300, Leandro Dorileo wrote:
> >> >> Cover basic aspects and API usage for QemuOpt. The current implementation
> >> >> covers the API's planned to be changed by Chunyan Liu in his
> >> >> QEMUOptionParameter
> >> >> replacement/cleanup job.
> >> >>
> >> >> Other APIs should be covered in future improvements.
> >> >>
> >> >> Signed-off-by: Leandro Dorileo <l@dorileo.org>
> >> >> Reviewed-by: Eric Blake <eblake@redhat.com>
> >> >> ---
> >> >> tests/Makefile | 3 +
> >> >> tests/test-qemu-opts.c | 455
> >> >> +++++++++++++++++++++++++++++++++++++++++++++++++
> >> >> 2 files changed, 458 insertions(+)
> >> >> create mode 100644 tests/test-qemu-opts.c
> >>
> >> I don't spot any test API or style issues; not familiar enough with
> >> QemuOpts to judge the tests though.
> >
> > What maintainer would best suite to route this patch?
>
> MAINTAINERS doesn't cover it. In the past year, patches went in via
> Anthony, Kevin, Luiz, or Stefan Hajnoczi. I'm cc'ing the ones from this
> list you missed.
Ok.
>
> I read your patch. There's some redundant testing, some comments feel
> superfluous, and there's a spelling mistake or two. Coverage is far
> from perfect (QemuOpts has become ridiculously complex), but infinitely
> better than before :)
>
Redundant testing don't seem to be a problem in this case, the comments are
intentionally verbose. My spell checker doesn't spot any spelling error -
besides "defval" :)
> Let's take it as is.
I'm respining the patch changing what Stefan suggested.
Thanks...
--
Leandro Dorileo
next prev parent reply other threads:[~2014-05-19 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 13:27 [Qemu-devel] [PATCH v3] QemuOpt: add unit tests Leandro Dorileo
2014-05-02 8:40 ` Stefan Hajnoczi
2014-05-19 21:33 ` Leandro Dorileo
[not found] ` <20140428185502.GA6934@dorilex>
[not found] ` <535EA5B4.1080301@suse.de>
[not found] ` <20140428211704.GA12444@dorilex>
[not found] ` <8738gvp6fp.fsf@blackfin.pond.sub.org>
2014-05-19 21:31 ` Leandro Dorileo [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-25 13:34 Leandro Dorileo
2014-03-25 13:26 Leandro Dorileo
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=20140519213102.GB2051@dorilex-lnv.MultilaserAP \
--to=l@dorileo.org \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=cyliu@suse.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wenchaoqemu@gmail.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).