qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PULL v2 0/9] M68k for 2.9 patches
Date: Sat, 14 Jan 2017 10:07:49 +0100	[thread overview]
Message-ID: <1484384878-29179-1-git-send-email-laurent@vivier.eu> (raw)

The following changes since commit b6af8ea60282df514f87d32e36afd1c9aeee28c8:

  Merge remote-tracking branch 'remotes/ehabkost/tags/x86-and-machine-pull-request' into staging (2017-01-13 14:38:21 +0000)

are available in the git repository at:

  git://github.com/vivier/qemu-m68k.git tags/m68k-for-2.9-pull-request

for you to fetch changes up to 727d937b59f1f722f983e20f9cd23b0e7ef60165:

  target-m68k: increment/decrement with SP (2017-01-14 10:06:21 +0100)

----------------------------------------------------------------
This is the list of the remaining patches that was part of series 
reviewed during the freeze period. They use the new new deposit
and extract ops.
There is also a cleanup patch from Thomas.

The v2 includes various fixes I've sent and that have been reviewed
since the first pull request.
----------------------------------------------------------------

Laurent Vivier (5):
  target-m68k: fix bit operation with immediate value
  target-m68k: fix gen_flush_flags()
  target-m68k: manage pre-dec et post-inc in CAS
  target-m68k: CAS doesn't need aligned access
  target-m68k: increment/decrement with SP

Richard Henderson (3):
  target-m68k: Implement bitfield ops for registers
  target-m68k: Implement bitfield ops for memory
  target-m68k: Implement bfffo

Thomas Huth (1):
  m68k: Remove PCI and USB from config file

 default-configs/m68k-softmmu.mak |   2 -
 target/m68k/cpu.h                |   1 +
 target/m68k/helper.h             |  10 +
 target/m68k/op_helper.c          | 206 +++++++++++++++++++
 target/m68k/translate.c          | 427 ++++++++++++++++++++++++++++++++++++++-
 5 files changed, 636 insertions(+), 10 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-01-14  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14  9:07 Laurent Vivier [this message]
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 1/9] target-m68k: Implement bitfield ops for registers Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 2/9] target-m68k: Implement bitfield ops for memory Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 3/9] target-m68k: Implement bfffo Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 4/9] m68k: Remove PCI and USB from config file Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 5/9] target-m68k: fix bit operation with immediate value Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 6/9] target-m68k: fix gen_flush_flags() Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 7/9] target-m68k: manage pre-dec et post-inc in CAS Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 8/9] target-m68k: CAS doesn't need aligned access Laurent Vivier
2017-01-14  9:07 ` [Qemu-devel] [PULL v2 9/9] target-m68k: increment/decrement with SP Laurent Vivier
2017-01-17 11:19 ` [Qemu-devel] [PULL v2 0/9] M68k for 2.9 patches 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=1484384878-29179-1-git-send-email-laurent@vivier.eu \
    --to=laurent@vivier.eu \
    --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).