From: Sangmoon Kim <sangmoon.kim@samsung.com>
To: Masahiro Yamada <masahiroy@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Sangmoon Kim <sangmoon.kim@samsung.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] docs: kbuild: remove description of KBUILD_LDS_MODULE
Date: Wed, 22 Feb 2023 09:45:50 +0900 [thread overview]
Message-ID: <20230222004550.13469-1-sangmoon.kim@samsung.com> (raw)
In-Reply-To: CGME20230222004609epcas1p2eb7e213b2b3503d018fcd6d58b9497b2@epcas1p2.samsung.com
Commit 596b0474d3d9 ("kbuild: preprocess module linker script")
has removed KBUILD_LDS_MODULE variable.
The KBUILD_LDS_MODULE variable is no longer available, so this patch
removes it from the document.
Signed-off-by: Sangmoon Kim <sangmoon.kim@samsung.com>
---
Documentation/kbuild/makefiles.rst | 5 -----
1 file changed, 5 deletions(-)
diff --git a/Documentation/kbuild/makefiles.rst b/Documentation/kbuild/makefiles.rst
index 38bc74eaa547..468e7830c1c3 100644
--- a/Documentation/kbuild/makefiles.rst
+++ b/Documentation/kbuild/makefiles.rst
@@ -1250,11 +1250,6 @@ When kbuild executes, the following steps are followed (roughly):
The linker script with full path. Assigned by the top-level Makefile.
- KBUILD_LDS_MODULE
-
- The module linker script with full path. Assigned by the top-level
- Makefile and additionally by the arch Makefile.
-
KBUILD_VMLINUX_OBJS
All object files for vmlinux. They are linked to vmlinux in the same
--
2.17.1
next parent reply other threads:[~2023-02-22 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230222004609epcas1p2eb7e213b2b3503d018fcd6d58b9497b2@epcas1p2.samsung.com>
2023-02-22 0:45 ` Sangmoon Kim [this message]
2023-02-22 7:33 ` [PATCH] docs: kbuild: remove description of KBUILD_LDS_MODULE Bagas Sanjaya
2023-02-22 10:47 ` [PATCH v2] " Sangmoon Kim
2023-02-22 16:21 ` Nathan Chancellor
2023-02-25 8:41 ` Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230222004550.13469-1-sangmoon.kim@samsung.com \
--to=sangmoon.kim@samsung.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox