From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: "David S. Miller " <davem@redhat.com>
Cc: netdev <netdev@oss.sgi.com>, linux-kernel@vger.kernel.org
Subject: [trivial] Use __init and __exit for sctp_init and sctp_exit
Date: Tue, 10 Dec 2002 18:55:02 +0530 [thread overview]
Message-ID: <20021210185502.G17375@in.ibm.com> (raw)
These module_init and module_exit routines should have been marked
__init and __exit like every where else I guess...
Please apply
Thanks,
Kiran
diff -ruN -X dontdiff linux-2.5.51/net/sctp/protocol.c sctp_fix-2.5.51/net/sctp/protocol.c
--- linux-2.5.51/net/sctp/protocol.c Tue Dec 10 08:16:10 2002
+++ sctp_fix-2.5.51/net/sctp/protocol.c Tue Dec 10 18:48:07 2002
@@ -598,7 +598,7 @@
}
/* Initialize the universe into something sensible. */
-int sctp_init(void)
+int __init sctp_init(void)
{
int i;
int status = 0;
@@ -751,7 +751,7 @@
}
/* Exit handler for the SCTP protocol. */
-void sctp_exit(void)
+void __exit sctp_exit(void)
{
/* BUG. This should probably do something useful like clean
* up all the remaining associations and all that memory.
reply other threads:[~2002-12-10 13:25 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=20021210185502.G17375@in.ibm.com \
--to=kiran@in.ibm.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).