From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: [PULL 0/1] M68k next patches
Date: Wed, 1 Feb 2023 10:54:01 +0100 [thread overview]
Message-ID: <20230201095402.1002350-1-laurent@vivier.eu> (raw)
The following changes since commit 13356edb87506c148b163b8c7eb0695647d00c2a:
Merge tag 'block-pull-request' of https://gitlab.com/stefanha/qemu into staging (2023-01-24 09:45:33 +0000)
are available in the Git repository at:
https://github.com/vivier/qemu-m68k.git tags/m68k-next-pull-request
for you to fetch changes up to c1fc91b82545a2b8ab73f81e5b7b6b0fec292ea1:
m68k: fix 'bkpt' instruction in softmmu mode (2023-02-01 10:18:21 +0100)
----------------------------------------------------------------
m68k pull request 20230201
fix 'bkpt' instruction in softmmu mode
----------------------------------------------------------------
Laurent Vivier (1):
m68k: fix 'bkpt' instruction in softmmu mode
target/m68k/translate.c | 4 ++++
1 file changed, 4 insertions(+)
--
2.39.1
next reply other threads:[~2023-02-01 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 9:54 Laurent Vivier [this message]
2023-02-01 9:54 ` [PULL 1/1] m68k: fix 'bkpt' instruction in softmmu mode Laurent Vivier
2023-02-04 17:16 ` [PULL 0/1] M68k next 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=20230201095402.1002350-1-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).