Lines Matching full:module

29 its configuration, reject loading the module or warn about a missing import.
31 Additionally, it is possible to put symbols into a module namespace, strictly
57 and kernel/module/main.c make use the namespace at build time or module load
93 Symbols exported using this macro are put into a module namespace. This
96 The macro takes a comma separated list of module names, allowing only those
111 load the module. The module code is required to use the macro MODULE_IMPORT_NS
112 for the namespaces it uses symbols from. E.g. a module using the
118 This will create a ``modinfo`` tag in the module for each imported namespace.
119 This has the side effect, that the imported namespaces of a module can be
128 It is advisable to add the MODULE_IMPORT_NS() statement close to other module
135 At module loading time (e.g. ``insmod``), the kernel will check each symbol
136 referenced from the module for its availability and whether the namespace it
137 might be exported to has been imported by the module. The default behaviour of
148 modpost will emit a warning if a module uses a symbol from a namespace
151 (along with other module meta data). To make the life of module authors (and
157 A typical scenario for module authors would be::
174 You can also run nsdeps for external module builds. A typical usage is::
178 Note: it will happily generate an import statement for the module namespace;