From: Nathan Froyd <froydnj@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Fix cpu_arm_handle_mmu_fault warning
Date: Mon, 26 Jan 2009 17:56:11 -0800 [thread overview]
Message-ID: <1233021372-15655-2-git-send-email-froydnj@codesourcery.com> (raw)
This patch fixes:
/scratch/froydnj/qemu.git/target-arm/helper.c:451: warning: no previous prototype for 'cpu_arm_handle_mmu_fault'
by moving the declaration of the function to cpu.h from exec.h. cpu.h
seems to be the place most other ports declare the corresponding
function.
Signed-off-by: Nathan Froyd <froydnj@codesourcery.com>
---
target-arm/cpu.h | 2 ++
target-arm/exec.h | 3 ---
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/target-arm/cpu.h b/target-arm/cpu.h
index 54c2c2e..cab80cd 100644
--- a/target-arm/cpu.h
+++ b/target-arm/cpu.h
@@ -217,6 +217,8 @@ uint32_t do_arm_semihosting(CPUARMState *env);
is returned if the signal was handled by the virtual CPU. */
int cpu_arm_signal_handler(int host_signum, void *pinfo,
void *puc);
+int cpu_arm_handle_mmu_fault (CPUARMState *env, target_ulong address, int rw,
+ int mmu_idx, int is_softmuu);
void cpu_lock(void);
void cpu_unlock(void);
diff --git a/target-arm/exec.h b/target-arm/exec.h
index b70e0cb..3e4083a 100644
--- a/target-arm/exec.h
+++ b/target-arm/exec.h
@@ -37,9 +37,6 @@ static inline void regs_to_env(void)
{
}
-int cpu_arm_handle_mmu_fault (CPUState *env, target_ulong address, int rw,
- int mmu_idx, int is_softmmu);
-
static inline int cpu_halted(CPUState *env) {
if (!env->halted)
return 0;
--
1.6.0.5
next reply other threads:[~2009-01-27 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 1:56 Nathan Froyd [this message]
2009-02-07 15:20 ` [Qemu-devel] [PATCH] Fix cpu_arm_handle_mmu_fault warning Aurelien Jarno
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=1233021372-15655-2-git-send-email-froydnj@codesourcery.com \
--to=froydnj@codesourcery.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).