From: Henne <henne@nachtwindheim.de>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] [PATCH] SN-subsys corrected patch
Date: Tue, 25 Apr 2006 14:35:00 +0000 [thread overview]
Message-ID: <444E3394.805@nachtwindheim.de> (raw)
Sorry,
I made a little mistake. Please remove my old sn_patch and take this one instead.
From: Henrik Kretzschmar <henne@nachtwindheim.de>
Marking the pci_driver_id tables of sn-subsystem as __devinitdata and
removing a bogus __devinitdata from ioc4's pci_driver table.
Signed-off-by: Henrik Kretzschmar <henne@nachtwindheim.de>
---
I hope nobody found out what happened in this pci_driver case.
diff -urN linux-2.6.17-rc2/drivers/sn/ioc3.c linux/drivers/sn/ioc3.c
--- linux-2.6.17-rc2/drivers/sn/ioc3.c 2006-04-24 13:31:01.000000000 +0200
+++ linux/drivers/sn/ioc3.c 2006-04-24 16:58:34.000000000 +0200
@@ -800,7 +800,7 @@
kfree(idd);
}
-static struct pci_device_id ioc3_id_table[] = {
+static struct pci_device_id ioc3_id_table[] __devinitdata = {
{PCI_VENDOR_ID_SGI, PCI_DEVICE_ID_SGI_IOC3, PCI_ANY_ID, PCI_ANY_ID},
{0}
};
diff -urN linux-2.6.17-rc2/drivers/sn/ioc4.c linux/drivers/sn/ioc4.c
--- linux-2.6.17-rc2/drivers/sn/ioc4.c 2006-04-24 13:31:01.000000000 +0200
+++ linux/drivers/sn/ioc4.c 2006-04-24 17:01:57.000000000 +0200
@@ -378,13 +378,13 @@
kfree(idd);
}
-static struct pci_device_id ioc4_id_table[] = {
+static struct pci_device_id ioc4_id_table[] __devinitdata = {
{PCI_VENDOR_ID_SGI, PCI_DEVICE_ID_SGI_IOC4, PCI_ANY_ID,
PCI_ANY_ID, 0x0b4000, 0xFFFFFF},
{0}
};
-static struct pci_driver __devinitdata ioc4_driver = {
+static struct pci_driver ioc4_driver __devinitdata = {
.name = "IOC4",
.id_table = ioc4_id_table,
.probe = ioc4_probe,
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
reply other threads:[~2006-04-25 14:35 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=444E3394.805@nachtwindheim.de \
--to=henne@nachtwindheim.de \
--cc=kernel-janitors@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.