From: peterhuewe@gmx.de
To: Jiri Kosina <trivial@kernel.org>
Cc: kernel-janitors@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/6] uwb/i1480: add __init/__exit macros
Date: Tue, 22 Dec 2009 09:27:05 +0100 [thread overview]
Message-ID: <1261470431-23642-1-git-send-email-peterhuewe@gmx.de> (raw)
From: Peter Huewe <peterhuewe@gmx.de>
Trivial patch which adds the __init/__exit macros to the module_init/
module_exit functions of
uwb/i1480/i1480-est.c
@Jiri: As there is no maintainer, it seems it is up to you to decide :)
Patch against linux-next-tree, 22. Dez 08:38:18 CET 2009
but also present in linus tree.
Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
---
drivers/uwb/i1480/i1480-est.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/uwb/i1480/i1480-est.c b/drivers/uwb/i1480/i1480-est.c
index 7bf8c6f..f2eb4d8 100644
--- a/drivers/uwb/i1480/i1480-est.c
+++ b/drivers/uwb/i1480/i1480-est.c
@@ -54,7 +54,7 @@ static struct uwb_est_entry i1480_est_fd01[] = {
.size = sizeof(struct i1480_rceb) + 2 },
};
-static int i1480_est_init(void)
+static int __init i1480_est_init(void)
{
int result = uwb_est_register(i1480_CET_VS1, 0x00, 0x8086, 0x0c3b,
i1480_est_fd00,
@@ -73,7 +73,7 @@ static int i1480_est_init(void)
}
module_init(i1480_est_init);
-static void i1480_est_exit(void)
+static void __exit i1480_est_exit(void)
{
uwb_est_unregister(i1480_CET_VS1, 0x00, 0x8086, 0x0c3b,
i1480_est_fd00, ARRAY_SIZE(i1480_est_fd00));
--
1.6.4.4
next reply other threads:[~2009-12-22 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 8:27 peterhuewe [this message]
2009-12-22 8:27 ` [PATCH 2/6] isdn/hardware: add __init/__exit macros to isdn/hardware/mISDN/mISDNisar.c peterhuewe
2010-01-05 10:22 ` Jiri Kosina
2009-12-22 8:51 ` [PATCH 1/6] uwb/i1480: add __init/__exit macros Marcel Holtmann
2009-12-22 8:57 ` Peter Hüwe
2009-12-22 9:08 ` Peter Hüwe
2009-12-22 12:20 ` David Vrabel
2009-12-22 13:13 ` Jiri Kosina
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=1261470431-23642-1-git-send-email-peterhuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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®