[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1222033928-25062-1-git-send-email-ukleinek@strlen.de>
Date: Sun, 21 Sep 2008 23:52:07 +0200
From: Uwe Kleine-König <ukleinek@...len.de>
To: linux-kernel@...r.kernel.org
Cc: Haavard Skinnemoen <haavard.skinnemoen@...el.com>
Subject: [PATCH] Use platform_driver_probe for pio platform driver
The probe function of the pio platform driver lives in the init section
and so a pio device that is created after the init section is discarded
probably results in an oops. Even if this cannot happen, using
platform_driver_probe is cleaner. (If this can happen and should be
supported the probe function must live in the devinit section instead.)
Signed-off-by: Uwe Kleine-König <ukleinek@...len.de>
Cc: Haavard Skinnemoen <haavard.skinnemoen@...el.com>
---
arch/avr32/mach-at32ap/pio.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/arch/avr32/mach-at32ap/pio.c b/arch/avr32/mach-at32ap/pio.c
index 405ee6b..96a6d5d 100644
--- a/arch/avr32/mach-at32ap/pio.c
+++ b/arch/avr32/mach-at32ap/pio.c
@@ -382,7 +382,6 @@ static int __init pio_probe(struct platform_device *pdev)
}
static struct platform_driver pio_driver = {
- .probe = pio_probe,
.driver = {
.name = "pio",
},
@@ -390,7 +389,7 @@ static struct platform_driver pio_driver = {
static int __init pio_init(void)
{
- return platform_driver_register(&pio_driver);
+ return platform_driver_probe(&pio_driver, pio_probe);
}
postcore_initcall(pio_init);
--
tg: (852b98c..) t/sectionfixes/pio (depends on: t/sectionfixes/h1940bt)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists