[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RFC PATCH] hw/intc: don't use target_ulong for LoongArch ipi
From: |
Alex Bennée |
Subject: |
[RFC PATCH] hw/intc: don't use target_ulong for LoongArch ipi |
Date: |
Tue, 4 Apr 2023 14:27:11 +0100 |
The calling function is already working with hwaddr and uint64_t so
lets avoid bringing target_ulong in if we don't need to.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
hw/intc/loongarch_ipi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/intc/loongarch_ipi.c b/hw/intc/loongarch_ipi.c
index aa4bf9eb74..bdba0f8107 100644
--- a/hw/intc/loongarch_ipi.c
+++ b/hw/intc/loongarch_ipi.c
@@ -50,7 +50,7 @@ static uint64_t loongarch_ipi_readl(void *opaque, hwaddr
addr, unsigned size)
return ret;
}
-static void send_ipi_data(CPULoongArchState *env, target_ulong val,
target_ulong addr)
+static void send_ipi_data(CPULoongArchState *env, uint64_t val, hwaddr addr)
{
int i, mask = 0, data = 0;
--
2.39.2
- [RFC PATCH] hw/intc: don't use target_ulong for LoongArch ipi,
Alex Bennée <=