From: Aurelien Jarno <aurelien@aurel32.net>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-sh4: Fix operands for fipr, ftrv instructions
Date: Sat, 7 Jan 2012 20:51:37 +0100 [thread overview]
Message-ID: <20120107195137.GC20302@volta.aurel32.net> (raw)
In-Reply-To: <1325765508-16066-1-git-send-email-sw@weilnetz.de>
On Thu, Jan 05, 2012 at 01:11:48PM +0100, Stefan Weil wrote:
> Coverity complained about right shifts of opcode (16, 18) which were
> larger than the size of opcode (16 bit).
>
> Using the correct shift values fixes this.
>
> Cc: Aurelien Jarno <aurelien@aurel32.net>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> target-sh4/translate.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Thanks, applied.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2012-01-07 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 12:11 [Qemu-devel] [PATCH] target-sh4: Fix operands for fipr, ftrv instructions Stefan Weil
2012-01-07 19:51 ` Aurelien Jarno [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=20120107195137.GC20302@volta.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).