DocBook: update EXPORT_SYMBOL entry to point at export.h
PATCH 1/1 DocBook: update EXPORT_SYMBOL entry to point at export.h
Previously we used to get EXPORT_SYMBOL and friends from module.h but we moved away from that since module.h largely includes the entire header space one way or another.
As most users just wanted the simple export related macros, they were spun off into a separate new header -- export.h Update the docs to reflect that.
---
[vectoring via trivial tree as RobL suggested for other doc patch]
Documentation/DocBook/kernel-hacking.tmpl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/DocBook/kernel-hacking.tmpl +2 -2
@@ -945,7 +945,7 @@ printk(KERN_INFO "my ip: %pI4\n", &ipaddress); <sect1 id="sym-exportsymbols"> <title><function>EXPORT_SYMBOL()</function> - <filename class="headerfile">include/linux/module.h</filename></title> + <filename class="headerfile">include/linux/export.h</filename></title> <para> This is the classic method of exporting a symbol: dynamically
@@ -955,7 +955,7 @@ printk(KERN_INFO "my ip: %pI4\n", &ipaddress); <sect1 id="sym-exportsymbols-gpl"> <title><function>EXPORT_SYMBOL_GPL()</function> - <filename class="headerfile">include/linux/module.h</filename></title> + <filename class="headerfile">include/linux/export.h</filename></title> <para> Similar to <function>EXPORT_SYMBOL()</function> except that the
Signature · 1 line
1.8.1.2
Quoted 4 lines · Paul Gortmaker
Previously we used to get
EXPORT_SYMBOLand friends frommodule.hbut we moved away from that sincemodule.hlargely includes the entire header space one way or another.
Quoted 8 lines
As most users just wanted the simple export related macros, they were spun off into a separate new header --
export.hUpdate the docs to reflect that.Suggested-by Borislav Petkov <[email protected]>Cc Rob Landley <[email protected]>Cc Jiri Kosina <[email protected]>Signed-off-by Paul Gortmaker <[email protected]>
Rob