Skip to contentSkip to conversation

__devinitdata on pci_device_tables

PATCH New Henne 1 participant 1 message Jul 6, 2006 Documentation

lore
Share & tools
lore

Henne

author
#0 lore raw

PATCH 1/1 __devinitdata on pci_device_tables

Since some section mismatches happend it doesn't seem to be a good idea to mark the pci_device_id tables as __devinitdata, so it should be mentioned in pci.txt .

From: Henrik Kretzschmar <[email protected]>

Correct the pci.txt about the __devintidata on pci_device_id tables.

---

Documentation/pci.txt 2006-07-06 12:02:10.000000000 +0200 renamed from Documentation/pci.txt 2006-07-06 10:41:43.000000000 +0200 +1 -1
@@ -122,7 +122,7 @@
        The module_init()/module_exit() functions (and all initialization
         functions called only from these) should be marked __init/exit.
        The struct pci_driver shouldn't be marked with any of these tags.
-       The ID table array should be marked __devinitdata.
+       The ID table array shouldn't be marked __devinitdata.
        The probe() and remove() functions (and all initialization
        functions called only from these) should be marked __devinit/exit.
        If you are sure the driver is not a hotplug driver then use only