From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/3] tricore-patches
Date: Sat, 30 May 2015 16:59:50 +0200 [thread overview]
Message-ID: <1432997993-25533-1-git-send-email-kbastian@mail.uni-paderborn.de> (raw)
The following changes since commit 97af820f539efe80b87615a04f9de11ea585f725:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20150529' into staging (2015-05-29 17:10:57 +0100)
are available in the git repository at:
https://github.com/bkoppelmann/qemu-tricore-upstream.git tags/pull-tricore-20150530
for you to fetch changes up to 07e15486faf353260431f10e85185372c5036baa:
target-tricore: fix BOL_ST_H_LONGOFF using ld (2015-05-30 16:49:19 +0200)
----------------------------------------------------------------
TriCore bugfixes
----------------------------------------------------------------
Bastian Koppelmann (3):
target-tricore: fix OPC2_32_RR_DVINIT_HU having write before use on the result
target-tricore: fix msub32_q producing the wrong overflow bit
target-tricore: fix BOL_ST_H_LONGOFF using ld
target-tricore/translate.c | 15 ++-------------
1 file changed, 2 insertions(+), 13 deletions(-)
--
2.4.2
next reply other threads:[~2015-05-30 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 14:59 Bastian Koppelmann [this message]
2015-05-30 14:59 ` [Qemu-devel] [PULL 1/3] target-tricore: fix OPC2_32_RR_DVINIT_HU having write before use on the result Bastian Koppelmann
2015-05-30 14:59 ` [Qemu-devel] [PULL 2/3] target-tricore: fix msub32_q producing the wrong overflow bit Bastian Koppelmann
2015-05-30 14:59 ` [Qemu-devel] [PULL 3/3] target-tricore: fix BOL_ST_H_LONGOFF using ld Bastian Koppelmann
2015-06-01 11:54 ` [Qemu-devel] [PULL 0/3] tricore-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=1432997993-25533-1-git-send-email-kbastian@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--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).