From: riku.voipio@linaro.org
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Riku Voipio <riku.voipio@linaro.org>
Subject: [Qemu-devel] [PULL 00/14] linux-user update
Date: Fri, 2 May 2014 22:15:35 +0300 [thread overview]
Message-ID: <cover.1399057853.git.riku.voipio@linaro.org> (raw)
From: Riku Voipio <riku.voipio@linaro.org>
The following changes since commit fdaad4715ae9e998fd0595bedfb16fdaf0c68ccc:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20140501' into staging (2014-05-02 11:32:00 +0100)
are available in the git repository at:
http://git.linaro.org/git/people/riku.voipio/qemu.git
for you to fetch changes up to ad6919dc0ab3b8ae26d772e883aa8e709785d249:
linux-user/elfload.c: Support ARM HWCAP2 flags (2014-05-02 21:59:36 +0300)
Huw Davies (2):
linux-user: Move if-elses to a switch statement.
linux-user: Add support for SCM_CREDENTIALS.
James Hogan (2):
linux-user: Assert stack used for auxvec, envp, argv
linux-user: Handle arches with llseek instead of _llseek
Maxim Ostapenko (1):
linux-user: Add /proc/self/exe open forwarding
Natanael Copa (1):
linux-user: avoid using glibc internals in _syscall5 and in definition
of target_sigevent struct
Peter Maydell (5):
linux-user/signal.c: Set fault address in AArch64 signal info
linux-user/elfload.c: Fix incorrect ARM HWCAP bits
linux-user/elfload.c: Update ARM HWCAP bits
linux-user/elfload.c: Fix A64 code which was incorrectly acting like
A32
linux-user/elfload.c: Support ARM HWCAP2 flags
Riku Voipio (3):
linux-user: rename cpu-uname -> uname
linux-user: move uname functions to uname.c
linux-user: remove configure option for setting uname release
configure | 8 ---
include/elf.h | 1 +
linux-user/Makefile.objs | 2 +-
linux-user/cpu-uname.c | 72 -------------------
linux-user/cpu-uname.h | 1 -
linux-user/elfload.c | 147 +++++++++++++++++++++++++++++++++-----
linux-user/main.c | 2 +-
linux-user/signal.c | 3 +-
linux-user/syscall.c | 178 +++++++++++++++-------------------------------
linux-user/syscall_defs.h | 16 ++++-
linux-user/uname.c | 171 ++++++++++++++++++++++++++++++++++++++++++++
linux-user/uname.h | 10 +++
12 files changed, 384 insertions(+), 227 deletions(-)
delete mode 100644 linux-user/cpu-uname.c
delete mode 100644 linux-user/cpu-uname.h
create mode 100644 linux-user/uname.c
create mode 100644 linux-user/uname.h
--
2.0.0.rc0
next reply other threads:[~2014-05-02 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 19:15 riku.voipio [this message]
2014-05-02 19:15 ` [Qemu-devel] [PULL 01/14] linux-user: Add /proc/self/exe open forwarding riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 02/14] linux-user: Assert stack used for auxvec, envp, argv riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 03/14] linux-user: Move if-elses to a switch statement riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 04/14] linux-user: Add support for SCM_CREDENTIALS riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 05/14] linux-user: Handle arches with llseek instead of _llseek riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 06/14] linux-user: avoid using glibc internals in _syscall5 and in definition of target_sigevent struct riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 07/14] linux-user/signal.c: Set fault address in AArch64 signal info riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 08/14] linux-user: rename cpu-uname -> uname riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 09/14] linux-user: move uname functions to uname.c riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 10/14] linux-user: remove configure option for setting uname release riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 11/14] linux-user/elfload.c: Fix incorrect ARM HWCAP bits riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 12/14] linux-user/elfload.c: Update " riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 13/14] linux-user/elfload.c: Fix A64 code which was incorrectly acting like A32 riku.voipio
2014-05-02 19:15 ` [Qemu-devel] [PULL 14/14] linux-user/elfload.c: Support ARM HWCAP2 flags 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=cover.1399057853.git.riku.voipio@linaro.org \
--to=riku.voipio@linaro.org \
--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).