diff options
author | Masahiro Yamada <masahiroy@kernel.org> | 2020-05-21 13:31:17 +0900 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2020-05-26 00:03:16 +0900 |
commit | 9504bbe91efc163e4c46496ae790da60353b23b4 (patch) | |
tree | eb8b953ac3ce7572dbd28e20de8fd62bc4498871 | |
parent | 8451791d1ff0fd229e3f5ef267a32423f5b5540f (diff) |
kbuild: doc: remove documentation about copying Module.symvers around
This is a left-over of commit 39808e451fdf ("kbuild: do not read
$(KBUILD_EXTMOD)/Module.symvers").
Kbuild no longer supports this way.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
-rw-r--r-- | Documentation/kbuild/modules.rst | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/Documentation/kbuild/modules.rst b/Documentation/kbuild/modules.rst index e0b45a257f21..a45cccff467d 100644 --- a/Documentation/kbuild/modules.rst +++ b/Documentation/kbuild/modules.rst @@ -528,18 +528,6 @@ build. will then do the expected and compile both modules with full knowledge of symbols from either module. - Use an extra Module.symvers file - When an external module is built, a Module.symvers file - is generated containing all exported symbols which are - not defined in the kernel. To get access to symbols - from bar.ko, copy the Module.symvers file from the - compilation of bar.ko to the directory where foo.ko is - built. During the module build, kbuild will read the - Module.symvers file in the directory of the external - module, and when the build is finished, a new - Module.symvers file is created containing the sum of - all symbols defined and not part of the kernel. - Use "make" variable KBUILD_EXTRA_SYMBOLS If it is impractical to add a top-level kbuild file, you can assign a space separated list |