From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI and sysfs fixes for 2.5.74
Date: Thu, 3 Jul 2003 19:09:12 -0700 [thread overview]
Message-ID: <10572845524168@kroah.com> (raw)
In-Reply-To: <10572845523317@kroah.com>
ChangeSet 1.1364, 2003/07/03 15:50:59-07:00, willy@debian.org
[PATCH] PCI: arch/i386/pci/direct.c can use __init, not __devinit
pci_sanity_check() is only called from functions marked __init, so it
can be __init too.
arch/i386/pci/direct.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nru a/arch/i386/pci/direct.c b/arch/i386/pci/direct.c
--- a/arch/i386/pci/direct.c Thu Jul 3 18:17:06 2003
+++ b/arch/i386/pci/direct.c Thu Jul 3 18:17:06 2003
@@ -177,7 +177,7 @@
* This should be close to trivial, but it isn't, because there are buggy
* chipsets (yes, you guessed it, by Intel and Compaq) that have no class ID.
*/
-static int __devinit pci_sanity_check(struct pci_raw_ops *o)
+static int __init pci_sanity_check(struct pci_raw_ops *o)
{
u32 x = 0;
int devfn;
next prev parent reply other threads:[~2003-07-04 2:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 2:06 [BK PATCH] PCI and sysfs fixes for 2.5.73 Greg KH
2003-07-04 2:09 ` [PATCH] PCI and sysfs fixes for 2.5.74 Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH [this message]
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 2:09 ` Greg KH
2003-07-04 6:52 ` [BK PATCH] PCI and sysfs fixes for 2.5.73 Dan Aloni
2003-07-04 17:05 ` 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=10572845524168@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 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.