From: Yongbok Kim <yongbok.kim@imgtec.com>
To: qemu-devel@nongnu.org
Cc: leon.alrae@imgtec.com, aurelien@aurel32.net
Subject: [Qemu-devel] [PATCH v4 03/15] target-mips: remove an unused argument
Date: Thu, 25 Jun 2015 00:24:15 +0100 [thread overview]
Message-ID: <1435188267-54510-4-git-send-email-yongbok.kim@imgtec.com> (raw)
In-Reply-To: <1435188267-54510-1-git-send-email-yongbok.kim@imgtec.com>
Remove an unused argument from decode_micromips32_opc()
Signed-off-by: Yongbok Kim <yongbok.kim@imgtec.com>
Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>
Reviewed-by: Aurelien Jarno <aurelien@aurel32.net>
---
target-mips/translate.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index 963ff8b..83dfb2f 100644
--- a/target-mips/translate.c
+++ b/target-mips/translate.c
@@ -13404,8 +13404,7 @@ static void gen_pool32fxf(DisasContext *ctx, int rt, int rs)
}
}
-static void decode_micromips32_opc (CPUMIPSState *env, DisasContext *ctx,
- uint16_t insn_hw1)
+static void decode_micromips32_opc(CPUMIPSState *env, DisasContext *ctx)
{
int32_t offset;
uint16_t insn;
@@ -14448,7 +14447,7 @@ static int decode_micromips_opc (CPUMIPSState *env, DisasContext *ctx)
generate_exception(ctx, EXCP_RI);
break;
default:
- decode_micromips32_opc (env, ctx, op);
+ decode_micromips32_opc(env, ctx);
return 4;
}
--
1.7.5.4
next prev parent reply other threads:[~2015-06-24 23:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 23:24 [Qemu-devel] [PATCH v4 00/15] target-mips: add microMIPS32 R6 Instruction Set support Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 01/15] target-mips: fix {RD, WR}PGPR in microMIPS Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 02/15] target-mips: add microMIPS TLBINV, TLBINVF Yongbok Kim
2015-06-24 23:24 ` Yongbok Kim [this message]
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 04/15] target-mips: refactor {D}LSA, {D}ALIGN, {D}BITSWAP Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 05/15] target-mips: rearrange gen_compute_compact_branch Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 06/15] target-mips: raise RI exceptions when FIR.PS = 0 Yongbok Kim
2015-06-25 22:06 ` Aurelien Jarno
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 07/15] target-mips: signal RI for removed instructions in microMIPS R6 Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 08/15] target-mips: add microMIPS32 R6 opcode enum Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 09/15] target-mips: microMIPS32 R6 branches and jumps Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 10/15] target-mips: microMIPS32 R6 POOL32A{XF} instructions Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 11/15] target-mips: microMIPS32 R6 POOL32F instructions Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 12/15] target-mips: microMIPS32 R6 POOL32{I, C} instructions Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 13/15] target-mips: microMIPS32 R6 Major instructions Yongbok Kim
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 14/15] target-mips: microMIPS32 R6 POOL16{A, C} instructions Yongbok Kim
2015-06-25 22:06 ` Aurelien Jarno
2015-06-24 23:24 ` [Qemu-devel] [PATCH v4 15/15] target-mips: add mips32r6-generic CPU definition Yongbok Kim
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=1435188267-54510-4-git-send-email-yongbok.kim@imgtec.com \
--to=yongbok.kim@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=leon.alrae@imgtec.com \
--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).