From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: OMAP2+: Fix is_gpmc_muxed warning for H4
Date: Thu, 18 Apr 2013 10:54:35 -0700 [thread overview]
Message-ID: <20130418175435.7436.60372.stgit@muffinssi.local> (raw)
In-Reply-To: <20130418175303.7436.75241.stgit@muffinssi.local>
Fix the following error by moving the function to be within
the smc91x related ifdef as that's the only user:
arch/arm/mach-omap2/board-h4.c:238: warning: ?is_gpmc_muxed? defined but not used
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
arch/arm/mach-omap2/board-h4.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/board-h4.c b/arch/arm/mach-omap2/board-h4.c
index 69c0acf..f745cae 100644
--- a/arch/arm/mach-omap2/board-h4.c
+++ b/arch/arm/mach-omap2/board-h4.c
@@ -229,6 +229,8 @@ static u32 get_sysboot_value(void)
OMAP2_SYSBOOT_1_MASK | OMAP2_SYSBOOT_0_MASK));
}
+#if IS_ENABLED(CONFIG_SMC91X)
+
/* H4-2420's always used muxed mode, H4-2422's always use non-muxed
*
* Note: OMAP-GIT doesn't correctly do is_cpu_omap2422 and is_cpu_omap2423
@@ -246,8 +248,6 @@ static u32 is_gpmc_muxed(void)
return 0;
}
-#if IS_ENABLED(CONFIG_SMC91X)
-
static struct omap_smc91x_platform_data board_smc91x_data = {
.cs = 1,
.gpio_irq = 92,
prev parent reply other threads:[~2013-04-18 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 17:54 [PATCH 0/3] few omap randconfig fixes for v3.10 Tony Lindgren
2013-04-18 17:54 ` [PATCH 1/3] ARM: OMAP2+: Fix unmet direct dependencies for SERIAL_OMAP Tony Lindgren
2013-04-18 17:54 ` [PATCH 2/3] ARM: OMAP2+: Fix unused variable warning for am3517 crane Tony Lindgren
2013-04-18 17:54 ` Tony Lindgren [this message]
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=20130418175435.7436.60372.stgit@muffinssi.local \
--to=tony@atomide.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