From: Kamil Rytarowski <n54@gmx.com>
To: Fam Zheng <famz@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] NetBSD maintenance
Date: Mon, 24 Apr 2017 09:54:57 +0200 [thread overview]
Message-ID: <838f86dd-70f4-83db-ce4d-7341728ba796@gmx.com> (raw)
In-Reply-To: <20170424072604.GE316@lemon.lan>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On 24.04.2017 09:26, Fam Zheng wrote:
> On Mon, 04/24 00:45, Kamil Rytarowski wrote:
>> I will have a look and try to build qemu from git (master branch).
>>
>> I also find it surprising that there was a call for CI machines and
>> there is no infrastructure for it.
>
> There are. We use travis and patchew. I don't know a lot about NetBSD testing
> with travis, but patchew has x86_64 and s390x machines that test patches, and
> welcomes more OSes/architectures:
>
> http://patchew.org/QEMU/20170423223216.17856-1-aurelien@aurel32.net/
>
> If qemu master can be build on NetBDS, I can create a VM for this on my x86_64
> machine, or you can generously contribute one, which is even better. :)
>
> Fam
>
That's great - we will be back to you when the build issues will be
sorted out.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-04-24 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 23:27 [Qemu-devel] NetBSD maintenance Kamil Rytarowski
2017-04-23 10:19 ` Peter Maydell
2017-04-23 22:45 ` Kamil Rytarowski
2017-04-24 7:26 ` Fam Zheng
2017-04-24 7:54 ` Kamil Rytarowski [this message]
2017-04-24 10:12 ` Peter Maydell
2017-04-25 13:49 ` Kamil Rytarowski
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=838f86dd-70f4-83db-ce4d-7341728ba796@gmx.com \
--to=n54@gmx.com \
--cc=famz@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).