From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] vt8500: Fix build warning when no framebuffer selected
Date: Sun, 7 Oct 2012 14:02:14 +1300 [thread overview]
Message-ID: <1349571734-26233-5-git-send-email-linux@prisktech.co.nz> (raw)
In-Reply-To: <1349571734-26233-1-git-send-email-linux@prisktech.co.nz>
Check for framebuffer defines before declaring variables in vt8500.c
Removes a compile-time warning about unused variables.
Signed-off-by: Tony Prisk <linux@prisktech.co.nz>
---
arch/arm/mach-vt8500/vt8500.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-vt8500/vt8500.c b/arch/arm/mach-vt8500/vt8500.c
index 7449886..a5bd286 100644
--- a/arch/arm/mach-vt8500/vt8500.c
+++ b/arch/arm/mach-vt8500/vt8500.c
@@ -75,8 +75,11 @@ static void vt8500_power_off(void)
void __init vt8500_init(void)
{
- struct device_node *np, *fb;
+ struct device_node *np;
+#if defined(CONFIG_FB_VT8500) || defined(CONFIG_FB_WM8505)
+ struct device_node *fb;
void __iomem *gpio_base;
+#endif
#ifdef CONFIG_FB_VT8500
fb = of_find_compatible_node(NULL, NULL, "via,vt8500-fb");
--
1.7.9.5
next prev parent reply other threads:[~2012-10-07 1:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 1:02 [PATCH 0/4] arm-soc: vt8500: Cleanup patches for 3.7 Tony Prisk
2012-10-07 1:02 ` [PATCH 1/4] vt8500: Remove unused headers from include/mach/ Tony Prisk
2012-10-07 1:02 ` [PATCH 2/4] vt8500: Remove arm/boot/compressed/head-vt8500.S Tony Prisk
2012-10-07 1:02 ` [PATCH 3/4] vt8500: Fix header in mach-vt8500/timer.c Tony Prisk
2012-10-07 1:02 ` Tony Prisk [this message]
2012-10-07 11:23 ` [PATCH 0/4] arm-soc: vt8500: Cleanup patches for 3.7 Arnd Bergmann
2012-10-07 14:19 ` Olof Johansson
2012-10-07 18:14 ` Tony Prisk
2012-10-07 18:21 ` Olof Johansson
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=1349571734-26233-5-git-send-email-linux@prisktech.co.nz \
--to=linux@prisktech.co.nz \
--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;
as well as URLs for NNTP newsgroup(s).