From: "Uwe Kleine-König" <ukleinek@strlen.de>
To: linux-kernel@vger.kernel.org
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Subject: [PATCH] Use platform_driver_probe for pdc platform driver
Date: Sun, 21 Sep 2008 23:52:08 +0200 [thread overview]
Message-ID: <1222033928-25062-2-git-send-email-ukleinek@strlen.de> (raw)
In-Reply-To: <1222033928-25062-1-git-send-email-ukleinek@strlen.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
The probe function of the pdc platform driver lives in the init section
and so a pdc 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@strlen.de>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
---
arch/avr32/mach-at32ap/pdc.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/arch/avr32/mach-at32ap/pdc.c b/arch/avr32/mach-at32ap/pdc.c
index 1040bda..61ab15a 100644
--- a/arch/avr32/mach-at32ap/pdc.c
+++ b/arch/avr32/mach-at32ap/pdc.c
@@ -35,7 +35,6 @@ static int __init pdc_probe(struct platform_device *pdev)
}
static struct platform_driver pdc_driver = {
- .probe = pdc_probe,
.driver = {
.name = "pdc",
},
@@ -43,6 +42,6 @@ static struct platform_driver pdc_driver = {
static int __init pdc_init(void)
{
- return platform_driver_register(&pdc_driver);
+ return platform_driver_probe(&pdc_driver, pdc_probe);
}
arch_initcall(pdc_init);
--
tg: (639920b..) t/sectionfixes/pdc (depends on: t/sectionfixes/pio)
next prev parent reply other threads:[~2008-09-21 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 21:52 [PATCH] Use platform_driver_probe for pio " Uwe Kleine-König
2008-09-21 21:52 ` Uwe Kleine-König [this message]
2008-09-22 8:30 ` [PATCH] Use platform_driver_probe for pdc " Haavard Skinnemoen
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=1222033928-25062-2-git-send-email-ukleinek@strlen.de \
--to=ukleinek@strlen.de \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®