* [PATCH] kbuild: doc: remove documentation about copying Module.symvers around
@ 2020-05-21 4:31 Masahiro Yamada
2020-05-26 10:28 ` Masahiro Yamada
0 siblings, 1 reply; 2+ messages in thread
From: Masahiro Yamada @ 2020-05-21 4:31 UTC (permalink / raw)
To: linux-kbuild
Cc: Jessica Yu, Masahiro Yamada, Jonathan Corbet, Michal Marek,
linux-doc, linux-kernel
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>
---
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] kbuild: doc: remove documentation about copying Module.symvers around
2020-05-21 4:31 [PATCH] kbuild: doc: remove documentation about copying Module.symvers around Masahiro Yamada
@ 2020-05-26 10:28 ` Masahiro Yamada
0 siblings, 0 replies; 2+ messages in thread
From: Masahiro Yamada @ 2020-05-26 10:28 UTC (permalink / raw)
To: Linux Kbuild mailing list
Cc: Jessica Yu, Jonathan Corbet, Michal Marek,
open list:DOCUMENTATION, Linux Kernel Mailing List
On Thu, May 21, 2020 at 1:31 PM Masahiro Yamada <masahiroy@kernel.org> 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@kernel.org>
> ---
>
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-05-26 10:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-21 4:31 [PATCH] kbuild: doc: remove documentation about copying Module.symvers around Masahiro Yamada
2020-05-26 10:28 ` Masahiro Yamada
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).