hc
2023-12-11 d2ccde1c8e90d38cee87a1b0309ad2827f3fd30d
kernel/Documentation/kernel-hacking/hacking.rst
....@@ -594,6 +594,24 @@
594594 maintainers and developers may however require EXPORT_SYMBOL_GPL()
595595 when adding any new APIs or functionality.
596596
597
+:c:func:`EXPORT_SYMBOL_NS()`
598
+----------------------------
599
+
600
+Defined in ``include/linux/export.h``
601
+
602
+This is the variant of `EXPORT_SYMBOL()` that allows specifying a symbol
603
+namespace. Symbol Namespaces are documented in
604
+:doc:`../core-api/symbol-namespaces`
605
+
606
+:c:func:`EXPORT_SYMBOL_NS_GPL()`
607
+--------------------------------
608
+
609
+Defined in ``include/linux/export.h``
610
+
611
+This is the variant of `EXPORT_SYMBOL_GPL()` that allows specifying a symbol
612
+namespace. Symbol Namespaces are documented in
613
+:doc:`../core-api/symbol-namespaces`
614
+
597615 Routines and Conventions
598616 ========================
599617
....@@ -718,7 +736,7 @@
718736 - Usually you want a configuration option for your kernel hack. Edit
719737 ``Kconfig`` in the appropriate directory. The Config language is
720738 simple to use by cut and paste, and there's complete documentation in
721
- ``Documentation/kbuild/kconfig-language.txt``.
739
+ ``Documentation/kbuild/kconfig-language.rst``.
722740
723741 In your description of the option, make sure you address both the
724742 expert user and the user who knows nothing about your feature.
....@@ -728,7 +746,7 @@
728746
729747 - Edit the ``Makefile``: the CONFIG variables are exported here so you
730748 can usually just add a "obj-$(CONFIG_xxx) += xxx.o" line. The syntax
731
- is documented in ``Documentation/kbuild/makefiles.txt``.
749
+ is documented in ``Documentation/kbuild/makefiles.rst``.
732750
733751 - Put yourself in ``CREDITS`` if you've done something noteworthy,
734752 usually beyond a single file (your name should be at the top of the