From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Felipe Balbi <balbi@ti.com>
Subject: [PATCH 1/5] arm: omap: debug-leds: drop machine_is_* checks
Date: Tue, 24 Jul 2012 11:53:58 +0300 [thread overview]
Message-ID: <1343120042-16695-2-git-send-email-balbi@ti.com> (raw)
In-Reply-To: <1343120042-16695-1-git-send-email-balbi@ti.com>
that platform_device is only registered by
board-h4.c, so there's no need to check which
machine is running as the driver won't bind
to anything.
Signed-off-by: Felipe Balbi <balbi@ti.com>
---
arch/arm/plat-omap/debug-leds.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/arch/arm/plat-omap/debug-leds.c b/arch/arm/plat-omap/debug-leds.c
index 39407cb..17cbef6 100644
--- a/arch/arm/plat-omap/debug-leds.c
+++ b/arch/arm/plat-omap/debug-leds.c
@@ -304,12 +304,6 @@ static struct platform_driver led_driver = {
static int __init fpga_init(void)
{
- if (machine_is_omap_h4()
- || machine_is_omap_h3()
- || machine_is_omap_h2()
- || machine_is_omap_perseus2()
- )
- return platform_driver_register(&led_driver);
- return 0;
+ return platform_driver_register(&led_driver);
}
fs_initcall(fpga_init);
--
1.7.11
next prev parent reply other threads:[~2012-07-24 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 8:53 [PATCH 0/5] arm: omap: debug-leds: few changes Felipe Balbi
2012-07-24 8:53 ` Felipe Balbi [this message]
2012-07-24 8:53 ` [PATCH 2/5] arm: omap: debug-leds: move initialization to debug-leds Felipe Balbi
2012-07-24 8:54 ` [PATCH 3/5] arm: omap: debug-leds: add section annotation to probe Felipe Balbi
2012-07-24 8:54 ` [PATCH 4/5] arm: omap: debug-leds: add a remove method Felipe Balbi
2012-07-24 8:54 ` [PATCH 5/5] arm: omap: debug-leds: switch to resource_size() Felipe Balbi
2012-09-07 22:32 ` [PATCH 0/5] arm: omap: debug-leds: few changes Tony Lindgren
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=1343120042-16695-2-git-send-email-balbi@ti.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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).