Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fabio.estevam@freescale.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mm/alignment.c: Fix build error
Date: Fri, 14 Oct 2011 15:11:47 -0300	[thread overview]
Message-ID: <1318615907-25391-1-git-send-email-fabio.estevam@freescale.com> (raw)

If CONFIG_PROC_FS is not set the following error is generated because
'cpu_is_v6_unaligned' definition is protected by CONFIG_PROC_FS:

CC      arch/arm/mm/alignment.o
arch/arm/mm/alignment.c: In function 'alignment_init':
arch/arm/mm/alignment.c:964: error: implicit declaration of function 'cpu_is_v6_unaligned'
arch/arm/mm/alignment.c:968: error: implicit declaration of function 'safe_usermode'
make[1]: *** [arch/arm/mm/alignment.o] Error 1
make: *** [arch/arm/mm] Error 2

This build error was triggered by 'make randconfig'.

Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
 arch/arm/mm/alignment.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mm/alignment.c b/arch/arm/mm/alignment.c
index cfbcf8b..38b270a 100644
--- a/arch/arm/mm/alignment.c
+++ b/arch/arm/mm/alignment.c
@@ -959,7 +959,6 @@ static int __init alignment_init(void)
 			  &alignment_proc_fops);
 	if (!res)
 		return -ENOMEM;
-#endif
 
 	if (cpu_is_v6_unaligned()) {
 		cr_alignment &= ~CR_A;
@@ -968,6 +967,7 @@ static int __init alignment_init(void)
 		ai_usermode = safe_usermode(ai_usermode, false);
 	}
 
+#endif
 	hook_fault_code(1, do_alignment, SIGBUS, BUS_ADRALN,
 			"alignment exception");
 
-- 
1.7.1

             reply	other threads:[~2011-10-14 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 18:11 Fabio Estevam [this message]
2011-10-14 18:26 ` [PATCH] ARM: mm/alignment.c: Fix build error Nicolas Pitre

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=1318615907-25391-1-git-send-email-fabio.estevam@freescale.com \
    --to=fabio.estevam@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.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