From: Kris Van Hees <kris.van.hees@oracle.com>
To: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-modules@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
Nick Alcock <nick.alcock@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Jiri Olsa <olsajiri@gmail.com>
Subject: [PATCH 6/6] module: add install target for modules.builtin.ranges
Date: Fri, 8 Dec 2023 00:07:52 -0500 [thread overview]
Message-ID: <20231208050752.2787575-7-kris.van.hees@oracle.com> (raw)
In-Reply-To: <20231208050752.2787575-1-kris.van.hees@oracle.com>
When CONFIG_BUILTIN_RANGES is enable, the modules.builtin.ranges file
should be installed in the module install location.
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
---
scripts/Makefile.modinst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/scripts/Makefile.modinst b/scripts/Makefile.modinst
index b45586aa1de4..f30f5ea04566 100644
--- a/scripts/Makefile.modinst
+++ b/scripts/Makefile.modinst
@@ -36,6 +36,11 @@ install-y += $(addprefix $(MODLIB)/, modules.builtin modules.builtin.modinfo mod
$(addprefix $(MODLIB)/, modules.builtin modules.builtin.modinfo modules.builtin.objs): $(MODLIB)/%: % FORCE
$(call cmd,install)
+install-$(CONFIG_BUILTIN_RANGES) += $(MODLIB)/modules.builtin.ranges
+
+$(MODLIB)/modules.builtin.ranges: modules.builtin.ranges FORCE
+ $(call cmd,install)
+
endif
modules := $(call read-file, $(MODORDER))
--
2.42.0
prev parent reply other threads:[~2023-12-08 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 5:07 [PATCH 0/6] Generate address range data for built-in modules Kris Van Hees
2023-12-08 5:07 ` [PATCH 1/6] kbuild: add modules.builtin.objs Kris Van Hees
2023-12-08 5:07 ` [PATCH 2/6] module: add CONFIG_BUILTIN_RANGES option Kris Van Hees
2023-12-08 22:59 ` Masami Hiramatsu
2023-12-11 16:29 ` Kris Van Hees
2023-12-08 5:07 ` [PATCH 3/6] kbuild: generate a linker map for vmlinux.o Kris Van Hees
2023-12-08 5:07 ` [PATCH 4/6] module: script to generate offset ranges for builtin modules Kris Van Hees
2023-12-08 5:07 ` [PATCH 5/6] kbuild: generate modules.builtin.ranges when linking the kernel Kris Van Hees
2023-12-08 5:07 ` Kris Van Hees [this message]
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=20231208050752.2787575-7-kris.van.hees@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nick.alcock@oracle.com \
--cc=olsajiri@gmail.com \
--cc=rostedt@goodmis.org \
/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
all inboxes | Powered by JetHome®