From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI Update for 2.6.3-rc1
Date: Mon, 9 Feb 2004 15:22:22 -0800 [thread overview]
Message-ID: <1076368942698@kroah.com> (raw)
In-Reply-To: <10763689422659@kroah.com>
ChangeSet 1.1500.11.19, 2004/02/04 17:23:50-08:00, eike-hotplug@sf-tec.de
[PATCH] PCI Hotplug: mark functions __init/__exit in acpiphp
These functions are only called from places marked __init or __exit, so
we can mark them also.
drivers/pci/hotplug/acpiphp_core.c | 6 +++---
drivers/pci/hotplug/acpiphp_glue.c | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff -Nru a/drivers/pci/hotplug/acpiphp_core.c b/drivers/pci/hotplug/acpiphp_core.c
--- a/drivers/pci/hotplug/acpiphp_core.c Mon Feb 9 14:58:29 2004
+++ b/drivers/pci/hotplug/acpiphp_core.c Mon Feb 9 14:58:29 2004
@@ -374,7 +374,7 @@
}
-static int init_acpi (void)
+static int __init init_acpi (void)
{
int retval;
@@ -426,7 +426,7 @@
* init_slots - initialize 'struct slot' structures for each slot
*
*/
-static int init_slots (void)
+static int __init init_slots (void)
{
struct slot *slot;
int retval = 0;
@@ -492,7 +492,7 @@
}
-static void cleanup_slots (void)
+static void __exit cleanup_slots (void)
{
struct list_head *tmp, *n;
struct slot *slot;
diff -Nru a/drivers/pci/hotplug/acpiphp_glue.c b/drivers/pci/hotplug/acpiphp_glue.c
--- a/drivers/pci/hotplug/acpiphp_glue.c Mon Feb 9 14:58:29 2004
+++ b/drivers/pci/hotplug/acpiphp_glue.c Mon Feb 9 14:58:29 2004
@@ -1056,7 +1056,7 @@
* acpiphp_glue_init - initializes all PCI hotplug - ACPI glue data structures
*
*/
-int acpiphp_glue_init (void)
+int __init acpiphp_glue_init(void)
{
int num;
@@ -1077,7 +1077,7 @@
*
* This function frees all data allocated in acpiphp_glue_init()
*/
-void acpiphp_glue_exit (void)
+void __exit acpiphp_glue_exit(void)
{
struct list_head *l1, *l2, *n1, *n2;
struct acpiphp_bridge *bridge;
@@ -1124,7 +1124,7 @@
/**
* acpiphp_get_num_slots - count number of slots in a system
*/
-int acpiphp_get_num_slots (void)
+int __init acpiphp_get_num_slots(void)
{
struct list_head *node;
struct acpiphp_bridge *bridge;
next prev parent reply other threads:[~2004-02-09 23:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 23:13 [BK PATCH] PCI update for 2.6.3-rc1 Greg KH
2004-02-09 23:22 ` [PATCH] PCI Update " Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH [this message]
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-09 23:22 ` Greg KH
2004-02-10 11:11 ` Marcelo Tosatti
2004-02-10 16:03 ` Geert Uytterhoeven
2004-02-10 16:46 ` Greg KH
2004-02-10 17:03 ` Kai Germaschewski
2004-02-10 17:49 ` Karsten Keil
2004-02-11 22:27 ` Adrian Bunk
2004-02-10 18:05 ` Adam Belay
2004-02-18 19:40 ` Greg KH
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=1076368942698@kroah.com \
--to=greg@kroah.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