From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] qom-test: Run for all available machines
Date: Thu, 23 Jan 2014 18:14:27 +0100 [thread overview]
Message-ID: <52E14DF3.9070006@suse.de> (raw)
In-Reply-To: <CAFEAcA_noKv4NJA16HP1udfD39Rjh7SSDd-p6_+MPKY0GpkybQ@mail.gmail.com>
Am 23.01.2014 17:00, schrieb Peter Maydell:
> On 23 January 2014 15:45, Andreas Färber <afaerber@suse.de> wrote:
>> I have also now sent out a patch covering Macs and e500. So the answer
>> is, I will accept a patch that has a reasonably small blacklist. The
>> time you're arguing about this on IRC and here you could've spent
>> actually helping investigate and fixing this... Even if I queued it and
>> sent a pull, it would take days or weeks to go in, so I really don't see
>> why I should rush this series into my tree.
>
> That's cool. I was only arguing because I was under the mistaken
> impression you didn't want to take this patch at all until
> everything was fixed.
Well, maybe "everything" is the misunderstanding here?
The following 3 patches address all my requests, ...
http://patchwork.ozlabs.org/patch/313620/
http://patchwork.ozlabs.org/patch/313642/
http://patchwork.ozlabs.org/patch/313659/
... and the first two would've been really easy to contribute for anyone
who cared about a proper white- or blacklist: introducing a new define
and taking away devices as long as everything still passes make check.
More cleanup would be possible (i8257) if we took away audio, too (sb16
etc.).
ppc40x was more involved, but still less than an hour to figure out.
Now waiting on Alex to review and send a pull or to ack for me to queue.
Having had to write these fixes myself now, maybe one of you two can
contribute the real QOM test of recursively walking properties via
qom-list and qom-get? :)
> I'm working on a patch which improves tests/Makefile so it
> autogenerates the list of sysemu-supporting targets and
> adds qom-test to the test list for all of them, so we don't
> even have to update the makefile when we add new architectures.
Appreciate it,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-01-23 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 13:31 [Qemu-devel] [PATCH 0/2] qom-test: Improve coverage armbru
2014-01-10 13:31 ` [Qemu-devel] [PATCH 1/2] qom-test: Run for all available machines armbru
2014-01-10 13:42 ` Markus Armbruster
2014-01-10 13:51 ` Alexander Graf
2014-01-10 14:17 ` Andreas Färber
2014-01-23 14:41 ` Andreas Färber
2014-01-23 15:40 ` Peter Maydell
2014-01-23 15:45 ` Andreas Färber
2014-01-23 16:00 ` Peter Maydell
2014-01-23 17:14 ` Andreas Färber [this message]
2014-01-23 14:54 ` Markus Armbruster
2014-01-31 12:33 ` Andreas Färber
2014-01-31 13:42 ` Markus Armbruster
2014-02-03 12:40 ` Markus Armbruster
2014-02-05 15:47 ` Andreas Färber
2014-02-05 17:51 ` Stefano Stabellini
2014-01-10 13:31 ` [Qemu-devel] [PATCH 2/2] qom-test: Test shutdown in addition to startup armbru
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=52E14DF3.9070006@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--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).