From: Riku Voipio <riku.voipio@iki.fi>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Richard Henderson <rth@twiddle.net>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/5] linux-user: safe_syscall updates
Date: Fri, 24 Jun 2016 12:08:47 +0300 [thread overview]
Message-ID: <20160624090847.GA33394@beaming.home> (raw)
In-Reply-To: <CAFEAcA-GaMKAOZ2S=H1_OmvpoJZcUNZzPQ8jNzzE8=95JqULrw@mail.gmail.com>
On Thu, Jun 23, 2016 at 01:10:40PM +0100, Peter Maydell wrote:
> On 22 June 2016 at 01:32, Richard Henderson <rth@twiddle.net> wrote:
> > Rebased on Riku's linux-user-for-upstream branch.
> > Fixed some nits that Peter pointed out.
> > Fixed the ppc64 version to properly return -errno.
> >
> > Retested all except s390x, which is, at the moment, inconvenient.
> I don't know enough s390/ppc to really review those two patches
> but they look right to me.
All pushed to linux-user, thanks!
https://git.linaro.org/people/riku.voipio/qemu.git/shortlog/refs/heads/linux-user-for-upstream
I'll craft a pull req to get these in well before soft freeze.
Riku
prev parent reply other threads:[~2016-06-24 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 0:32 [Qemu-devel] [PATCH v2 0/5] linux-user: safe_syscall updates Richard Henderson
2016-06-22 0:32 ` [Qemu-devel] [PATCH v2 1/5] linux-user: Provide safe_syscall for i386 Richard Henderson
2016-06-23 12:06 ` Peter Maydell
2016-06-22 0:32 ` [Qemu-devel] [PATCH v2 2/5] linux-user: Provide safe_syscall for arm Richard Henderson
2016-06-22 0:32 ` [Qemu-devel] [PATCH v2 3/5] linux-user: Provide safe_syscall for aarch64 Richard Henderson
2016-06-23 12:06 ` Peter Maydell
2016-06-22 0:32 ` [Qemu-devel] [PATCH v2 4/5] linux-user: Provide safe_syscall for s390x Richard Henderson
2016-06-22 0:32 ` [Qemu-devel] [PATCH v2 5/5] linux-user: Provide safe_syscall for ppc64 Richard Henderson
2016-06-23 12:10 ` [Qemu-devel] [PATCH v2 0/5] linux-user: safe_syscall updates Peter Maydell
2016-06-24 9:08 ` Riku Voipio [this message]
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=20160624090847.GA33394@beaming.home \
--to=riku.voipio@iki.fi \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).