On Thu, May 21, 2020 at 1:31 PM Masahiro Yamada <masahiroy@xxxxxxxxxx> wrote:
>
> 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@xxxxxxxxxx>
> ---
>
Applied to linux-kbuild.
> Documentation/kbuild/modules.rst | 12 ------------
> 1 file changed, 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
> --
> 2.25.1
>
--
Best Regards
Masahiro Yamada
