Lines Matching refs:namespace

25 documentation purposes (think of the SUBSYSTEM_DEBUG namespace) as well as for
28 are required to import the namespace. Otherwise the kernel will, depending on
34 Symbols can be exported into namespace using different methods. All of them are
43 available to export symbols into a certain namespace: EXPORT_SYMBOL_NS() and
44 EXPORT_SYMBOL_NS_GPL(). They take one additional argument: the namespace.
47 namespace ``USB_STORAGE``, use::
52 ``namespace`` set accordingly. A symbol that is exported without a namespace will
53 refer to ``NULL``. There is no default namespace if none is defined. ``modpost``
54 and kernel/module/main.c make use the namespace at build time or module load
63 and EXPORT_SYMBOL_GPL() macro expansions that do not specify a namespace.
67 is to define the default namespace in the ``Makefile`` of the subsystem. E.g. to
68 export all symbols defined in usb-common into the namespace USB_COMMON, add a
75 still be exported into the namespace that is passed as the namespace argument
76 as this argument has preference over a default symbol namespace.
78 A second option to define the default namespace is directly in the compilation
94 usb_stor_suspend symbol from above, needs to import the namespace USB_STORAGE
99 This will create a ``modinfo`` tag in the module for each imported namespace.
117 referenced from the module for its availability and whether the namespace it
129 modpost will emit a warning if a module uses a symbol from a namespace
140 	- write code that depends on a symbol from a not imported namespace
145 For subsystem maintainers introducing a namespace, the steps are very similar.
146 Again, ``make nsdeps`` will eventually add the missing namespace imports for
149 	- move or add symbols to a namespace (e.g. with EXPORT_SYMBOL_NS())