public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: a.zummo@towertech.it, linux-kernel@vger.kernel.org
Cc: Ben Dooks <ben-linux@fluff.org>
Subject: RTC: rtc-s3c: add __devexit and __devinit markers
Date: Sun, 20 Jul 2008 17:14:18 +0100	[thread overview]
Message-ID: <20080720161418.186584460@fluff.org.uk> (raw)

[-- Attachment #1: simtec/simtec-s3c24xx-rtc-devattr.patch --]
[-- Type: text/plain, Size: 1280 bytes --]

Add the relevant __devinit and __devexit attributes to
the rtc-s3c driver.

Signed-off-by: Ben Dooks <ben-linux@fluff.org>

Index: linux-2.6.26-quilt3/drivers/rtc/rtc-s3c.c
===================================================================
--- linux-2.6.26-quilt3.orig/drivers/rtc/rtc-s3c.c	2008-07-20 17:08:20.000000000 +0100
+++ linux-2.6.26-quilt3/drivers/rtc/rtc-s3c.c	2008-07-20 17:09:00.000000000 +0100
@@ -383,7 +383,7 @@ static void s3c_rtc_enable(struct platfo
 	}
 }
 
-static int s3c_rtc_remove(struct platform_device *dev)
+static int __devexit s3c_rtc_remove(struct platform_device *dev)
 {
 	struct rtc_device *rtc = platform_get_drvdata(dev);
 
@@ -400,7 +400,7 @@ static int s3c_rtc_remove(struct platfor
 	return 0;
 }
 
-static int s3c_rtc_probe(struct platform_device *pdev)
+static int __devinit s3c_rtc_probe(struct platform_device *pdev)
 {
 	struct rtc_device *rtc;
 	struct resource *res;
@@ -513,7 +513,7 @@ static int s3c_rtc_resume(struct platfor
 
 static struct platform_driver s3c2410_rtcdrv = {
 	.probe		= s3c_rtc_probe,
-	.remove		= s3c_rtc_remove,
+	.remove		= __devexit_p(s3c_rtc_remove),
 	.suspend	= s3c_rtc_suspend,
 	.resume		= s3c_rtc_resume,
 	.driver		= {

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

             reply	other threads:[~2008-07-20 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 16:14 Ben Dooks [this message]
2008-07-20 20:36 ` RTC: rtc-s3c: add __devexit and __devinit markers Alessandro Zummo

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=20080720161418.186584460@fluff.org.uk \
    --to=ben-linux@fluff.org \
    --cc=a.zummo@towertech.it \
    --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