Skip to contentSkip to conversation

kbuild: doc: remove documentation about copying Module.symvers around

PATCH In review Masahiro Yamada 1 participant 2 messages May 21, 2020 – May 26, 2020

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 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.

---

 Documentation/kbuild/modules.rst | 12 ------------
 1 file changed, 12 deletions(-)
Documentation/kbuild/modules.rst +0 -12
index e0b45a257f21..a45cccff467d 100644
@@ -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
Signature · 1 line
2.25.1
#1 lore raw
Quoted 9 lines · Masahiro Yamada

This is a left-over of commit 39808e451fdf ("kbuild: do not read $(KBUILD_EXTMOD)/Module.symvers").

Kbuild no longer supports this way.

---

Applied to linux-kbuild.

Quoted 29 lines
 Documentation/kbuild/modules.rst | 12 ------------
 1 file changed, 12 deletions(-)
Documentation/kbuild/modules.rst +0 -13
index e0b45a257f21..a45cccff467d 100644
@@ -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
--

2.25.1

Signature · 2 lines
Best Regards
Masahiro Yamada