Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: a.othieno@bluewin.ch (Arthur Othieno)
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: [PATCH] mips: prom_free_prom_memory() returns `unsigned long'
Date: Fri, 28 Oct 2005 00:42:56 -0400	[thread overview]
Message-ID: <20051028044256.GA14758@krypton> (raw)

Hi,

Some boards have, eg.:

  arch/mips/momentum/ocelot_3/prom.c:242:void __init prom_free_prom_memory(void)

yet free_initmem() expects a return:

  arch/mips/mm/init.c:285:extern unsigned long prom_free_prom_memory(void);
  arch/mips/mm/init.c:291:	freed = prom_free_prom_memory();

Fix those up and return 0 instead, just like everyone else does.

Signed-off-by: Arthur Othieno <a.othieno@bluewin.ch>

---

 arch/mips/momentum/jaguar_atx/prom.c |    3 ++-
 arch/mips/momentum/ocelot_3/prom.c   |    3 ++-
 arch/mips/pmc-sierra/yosemite/prom.c |    3 ++-
 3 files changed, 6 insertions(+), 3 deletions(-)

718345abbb965ef544659d6cb0e90dee1535107b
diff --git a/arch/mips/momentum/jaguar_atx/prom.c b/arch/mips/momentum/jaguar_atx/prom.c
--- a/arch/mips/momentum/jaguar_atx/prom.c
+++ b/arch/mips/momentum/jaguar_atx/prom.c
@@ -236,8 +236,9 @@ void __init prom_init(void)
 #endif
 }
 
-void __init prom_free_prom_memory(void)
+unsigned long __init prom_free_prom_memory(void)
 {
+	return 0;
 }
 
 void __init prom_fixup_mem_map(unsigned long start, unsigned long end)
diff --git a/arch/mips/momentum/ocelot_3/prom.c b/arch/mips/momentum/ocelot_3/prom.c
--- a/arch/mips/momentum/ocelot_3/prom.c
+++ b/arch/mips/momentum/ocelot_3/prom.c
@@ -239,8 +239,9 @@ void __init prom_init(void)
 #endif
 }
 
-void __init prom_free_prom_memory(void)
+unsigned long __init prom_free_prom_memory(void)
 {
+	return 0;
 }
 
 void __init prom_fixup_mem_map(unsigned long start, unsigned long end)
diff --git a/arch/mips/pmc-sierra/yosemite/prom.c b/arch/mips/pmc-sierra/yosemite/prom.c
--- a/arch/mips/pmc-sierra/yosemite/prom.c
+++ b/arch/mips/pmc-sierra/yosemite/prom.c
@@ -132,8 +132,9 @@ void __init prom_init(void)
 	prom_grab_secondary();
 }
 
-void __init prom_free_prom_memory(void)
+unsigned long __init prom_free_prom_memory(void)
 {
+	return 0;
 }
 
 void __init prom_fixup_mem_map(unsigned long start, unsigned long end)

             reply	other threads:[~2005-10-28  4:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28  4:42 Arthur Othieno [this message]
2005-10-28 10:12 ` [PATCH] mips: prom_free_prom_memory() returns `unsigned long' Ralf Baechle

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=20051028044256.GA14758@krypton \
    --to=a.othieno@bluewin.ch \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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