qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PULL] v2: pending linux-user patches
Date: Tue, 19 Jul 2011 08:01:33 -0500	[thread overview]
Message-ID: <4E25802D.8040800@codemonkey.ws> (raw)
In-Reply-To: <20110718073721.GA29548@afflict.kos.to>

On 07/18/2011 02:37 AM, Riku Voipio wrote:
> The following changes since commit 89b9ba661bd2d6155308f895ec075d813f0e129b:
>
>    Fix signal handling of SIG_IPI when io-thread is enabled (2011-07-16 19:43:00 +0000)

Pulled.  Thanks.

Regards,

Anthony Liguori

>
> are available in the git repository at:
>    git://git.linaro.org/people/rikuvoipio/qemu.git linux-user-for-upstream
>
> Cédric VINCENT (4):
>        arm-semi: Provide access to CLI arguments passed through the "-append" option
>        linux-user: Add support for KD...LED ioctls
>        linux-user: Add support for more VT ioctls
>        linux-user: Add support for even more FB ioctls
>
> Peter Maydell (4):
>        linux-user: Add syscall numbers from kernel 2.6.39.2
>        linux-user: Implement prlimit64 syscall
>        linux-user/syscall.c: Enforce pselect6 sigset size restrictions
>        linux-user/signal.c: Rename s390 target_ucontext fields to fix ia64
>
> Riku Voipio (2):
>        linux-user: correct syscall 123 on sh4
>        linux-user: make MIPS and ARM eabi use same argument reordering
>
> Wesley W. Terpstra (5):
>        mips: sigaltstack args
>        mips: missing syscall returns wrong errno
>        mips: null pointer deref should segfault
>        mips: rlimit incorrectly converts values
>        mips: rlimit codes are not the same
>
>   arm-semi.c                         |  113 ++++++++++++++++-----------
>   linux-user/alpha/syscall_nr.h      |   23 +++++-
>   linux-user/arm/syscall_nr.h        |   13 +++
>   linux-user/cris/syscall_nr.h       |    2 +
>   linux-user/i386/syscall_nr.h       |   12 +++
>   linux-user/ioctls.h                |   13 +++
>   linux-user/m68k/syscall_nr.h       |   16 ++++
>   linux-user/main.c                  |   33 +++++++-
>   linux-user/microblaze/syscall_nr.h |   14 +++-
>   linux-user/mips/syscall_nr.h       |   13 +++
>   linux-user/mips64/syscall_nr.h     |   13 +++
>   linux-user/mipsn32/syscall_nr.h    |   14 +++
>   linux-user/ppc/syscall_nr.h        |   30 +++++++
>   linux-user/s390x/syscall_nr.h      |   13 +++-
>   linux-user/sh4/syscall_nr.h        |   34 ++++++++-
>   linux-user/signal.c                |   30 ++++----
>   linux-user/sparc/syscall_nr.h      |   12 +++
>   linux-user/sparc64/syscall_nr.h    |   12 +++
>   linux-user/syscall.c               |  153 +++++++++++++++++++++++++++++-------
>   linux-user/syscall_defs.h          |   51 ++++++++++++
>   linux-user/syscall_types.h         |   20 +++++
>   linux-user/x86_64/syscall_nr.h     |   12 +++
>   22 files changed, 549 insertions(+), 97 deletions(-)
>
>
>

      reply	other threads:[~2011-07-19 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18  7:37 [Qemu-devel] [PULL] v2: pending linux-user patches Riku Voipio
2011-07-19 13:01 ` Anthony Liguori [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=4E25802D.8040800@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).