From: Peter Maydell <peter.maydell@linaro.org>
To: Tobias Nygren <tnn@netbsd.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] user-exec.c: fix build on NetBSD/sparc64 and NetBSD/arm
Date: Sun, 8 Mar 2015 19:27:27 +0900 [thread overview]
Message-ID: <CAFEAcA-ktasM7twVKwZ8TP19YLTR1ZYbGKUJCSe=9y1WwypdrA@mail.gmail.com> (raw)
In-Reply-To: <1425591461-17550-1-git-send-email-tnn@NetBSD.org>
On 6 March 2015 at 06:37, Tobias Nygren <tnn@netbsd.org> wrote:
> A couple of #ifdef changes necessary to use NetBSD's ucontext
> structs on sparc64 and arm.
>
> Signed-off-by: Tobias Nygren <tnn@NetBSD.org>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Does NetBSD have a big stack of out-of-tree patches for QEMU,
or do you run basically stock upstream QEMU?
thanks
-- PMM
next prev parent reply other threads:[~2015-03-08 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 21:37 [Qemu-devel] [PATCH] user-exec.c: fix build on NetBSD/sparc64 and NetBSD/arm Tobias Nygren
2015-03-08 10:27 ` Peter Maydell [this message]
2015-03-08 12:37 ` Tobias Nygren
2015-03-08 12:53 ` Peter Maydell
2015-03-08 14:59 ` Tobias Nygren
2015-03-08 15:01 ` Peter Maydell
2015-03-13 16:38 ` Peter Maydell
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='CAFEAcA-ktasM7twVKwZ8TP19YLTR1ZYbGKUJCSe=9y1WwypdrA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tnn@netbsd.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).