From: Henne <henne@nachtwindheim.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] __devinitdata on pci_device_tables
Date: Thu, 06 Jul 2006 12:14:21 +0200 [thread overview]
Message-ID: <44ACE27D.1010108@nachtwindheim.de> (raw)
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 <henne@nachtwindheim.de>
Correct the pci.txt about the __devintidata on pci_device_id tables.
Signed-off-by: Henrik Kretzschmar <henne@nachtwindheim.de>
---
--- linux-2.6.18-rc1/Documentation/pci.txt 2006-07-06 10:41:43.000000000 +0200
+++ linux/Documentation/pci.txt 2006-07-06 12:02:10.000000000 +0200
@@ -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
reply other threads:[~2006-07-06 10:11 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=44ACE27D.1010108@nachtwindheim.de \
--to=henne@nachtwindheim.de \
--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