From: David Daney <ddaney@caviumnetworks.com>
To: linux-mips <linux-mips@linux-mips.org>,
"Ralf Baechle" <ralf@linux-mips.org>,
"Ralf Rösch" <ralf.roesch@rw-gmbh.de>
Subject: Fwd: check_for_high_segbits not used when 32bit
Date: Fri, 30 Apr 2010 09:57:46 -0700 [thread overview]
Message-ID: <4BDB0C0A.1060506@caviumnetworks.com> (raw)
Sorry about that.
Perhaps you can send it with a Signed-off-by: to lmo.
David Daney
-------- Original Message --------
Subject: check_for_high_segbits not used when 32bit
Date: Fri, 30 Apr 2010 17:57:53 +0200
From: Ralf Rösch <ralf.roesch@rw-gmbh.de>
To: ddaney@caviumnetworks.com
Hi David,
check_for_high_segbits are only used when 64 bit kernel.
CC arch/mips/mm/tlbex.o
cc1: warnings being treated as errors
/pub/build/linux-mips/work-2.6/arch/mips/mm/tlbex.c:172: error:
‘check_for_high_segbits’ defined but not used
make[6]: *** [arch/mips/mm/tlbex.o] Fehler 1
regards
Ralf
diff --git a/arch/mips/mm/tlbex.c b/arch/mips/mm/tlbex.c
index e60ea35..86f004d 100644
--- a/arch/mips/mm/tlbex.c
+++ b/arch/mips/mm/tlbex.c
@@ -169,7 +169,9 @@ static u32 tlb_handler[128] __cpuinitdata;
static struct uasm_label labels[128] __cpuinitdata;
static struct uasm_reloc relocs[128] __cpuinitdata;
+#ifdef CONFIG_64BIT
static int check_for_high_segbits __cpuinitdata;
+#endif
#ifndef CONFIG_MIPS_PGD_C0_CONTEXT
/*
--
Roesch& Walter___________________________________________
Industrie-Elektronik GmbH * Tel.: +49-7824 / 6628-0
Wörtelweg 2b/c * Fax: +49-7824 / 6628-29
D-77963 Schwanau * mailto:ralf.roesch@rw-gmbh.de
Germany * WWW: http://www.rw-gmbh.de
Amtsgericht Freiburg i.Br. HRB 391345
Geschäftsführer: Dipl.Ing.(FH) Ralf Rösch, Dipl.Ing.(FH) Martin Walter
next reply other threads:[~2010-04-30 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 16:57 David Daney [this message]
2010-04-30 17:12 ` Fwd: check_for_high_segbits not used when 32bit 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=4BDB0C0A.1060506@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf.roesch@rw-gmbh.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.