From: Christoph Hellwig <hch@lst.de>
To: arndb@arndb.de
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH] spufs: fix section conflicts
Date: Thu, 6 Apr 2006 16:12:17 +0200 [thread overview]
Message-ID: <20060406141217.GA9329@lst.de> (raw)
spufs_init/spufs_exit call various __init/__exit functions so they
need to be marked __init/__exit aswell to not get section conflicts.
Also move the module_init call to where it belongs.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/arch/powerpc/platforms/cell/spufs/inode.c
===================================================================
--- linux-2.6.orig/arch/powerpc/platforms/cell/spufs/inode.c 2006-04-06 15:53:42.000000000 +0200
+++ linux-2.6/arch/powerpc/platforms/cell/spufs/inode.c 2006-04-06 15:56:21.000000000 +0200
@@ -442,7 +442,7 @@
.kill_sb = kill_litter_super,
};
-static int spufs_init(void)
+static int __init spufs_init(void)
{
int ret;
ret = -ENOMEM;
@@ -470,15 +470,16 @@
out:
return ret;
}
-module_init(spufs_init);
-static void spufs_exit(void)
+static void __exit spufs_exit(void)
{
spu_sched_exit();
unregister_spu_syscalls(&spufs_calls);
unregister_filesystem(&spufs_type);
kmem_cache_destroy(spufs_inode_cache);
}
+
+module_init(spufs_init);
module_exit(spufs_exit);
MODULE_LICENSE("GPL");
reply other threads:[~2006-04-06 14:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060406141217.GA9329@lst.de \
--to=hch@lst.de \
--cc=arndb@arndb.de \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.