From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>,
Richard Henderson <rth@twiddle.net>,
Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PATCH v4 0/1] target/m68k, linux-user: manage FP registers in ucontext
Date: Thu, 14 Sep 2017 18:35:04 +0200 [thread overview]
Message-ID: <20170914163505.20558-1-laurent@vivier.eu> (raw)
v3:
rebase and add R-b from rth
should also fix patchew errors as the missing commits
are now in the master
v2:
add missing cpu_m68k_set_fpcr() to update FPU internal state
The v1 was in the v5 of the series "target-m68k: implement 680x0 FPU"
Laurent Vivier (1):
target/m68k,linux-user: manage FP registers in ucontext
linux-user/signal.c | 43 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+)
--
2.13.5
next reply other threads:[~2017-09-14 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 16:35 Laurent Vivier [this message]
2017-09-14 16:35 ` [Qemu-devel] [PATCH v4 1/1] target/m68k, linux-user: manage FP registers in ucontext Laurent Vivier
2017-10-16 12:27 ` Riku Voipio
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=20170914163505.20558-1-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--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).