From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: [v2 1/2] kbuild: move scripts/mod/ build to modules_prepare
Date: Sat, 14 May 2022 13:02:06 +0900 [thread overview]
Message-ID: <20220514040207.282910-1-masahiroy@kernel.org> (raw)
Do $(build)=scripts/mod after $(build)=. so that
scripts/mod/devicetable-offsets.c can use headers generated by ./Kbuild.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---
Changes for v2:
- New patch to fix errors reported by 0-day bot
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index f90fcc1a7ff4..baa3440aea7f 100644
--- a/Makefile
+++ b/Makefile
@@ -1190,7 +1190,6 @@ archprepare: outputmakefile archheaders archscripts scripts include/config/kerne
include/generated/autoconf.h remove-stale-files
prepare0: archprepare
- $(Q)$(MAKE) $(build)=scripts/mod
$(Q)$(MAKE) $(build)=.
# All the preparing..
@@ -1441,6 +1440,7 @@ targets += modules.order
PHONY += modules_prepare
modules_prepare: prepare
$(Q)$(MAKE) $(build)=scripts scripts/module.lds
+ $(Q)$(MAKE) $(build)=scripts/mod
export modules_sign_only :=
--
2.32.0
next reply other threads:[~2022-05-14 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 4:02 Masahiro Yamada [this message]
2022-05-14 4:02 ` [v2 2/2] kbuild: copy scripts/atomic/atomic-*.h to include/generated/atomic-*.h Masahiro Yamada
2022-05-16 8:42 ` Mark Rutland
2022-05-16 9:30 ` Masahiro Yamada
2022-05-19 9:16 ` Mark Rutland
2022-05-16 6:02 ` [v2 1/2] kbuild: move scripts/mod/ build to modules_prepare kernel test robot
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=20220514040207.282910-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mark.rutland@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.