From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Greentime Hu <green.hu@gmail.com>, Nick Hu <nickhu@andestech.com>,
Vincent Chen <deanbo422@gmail.com>
Subject: [PATCH] nds32: move core-y in arch/nds32/Makefile to arch/nds32/Kbuild
Date: Mon, 14 Feb 2022 12:37:24 +0900 [thread overview]
Message-ID: <20220214033724.2409951-1-masahiroy@kernel.org> (raw)
Use obj-y to clean up Makefile.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---
arch/nds32/Kbuild | 3 +++
arch/nds32/Makefile | 3 ---
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/nds32/Kbuild b/arch/nds32/Kbuild
index 4e39f7abdeb6..ac127371afa4 100644
--- a/arch/nds32/Kbuild
+++ b/arch/nds32/Kbuild
@@ -1,4 +1,7 @@
# SPDX-License-Identifier: GPL-2.0-only
+obj-y += kernel/ mm/
+obj-$(CONFIG_FPU) += math-emu/
+obj-y += boot/dts/
# for cleaning
subdir- += boot
diff --git a/arch/nds32/Makefile b/arch/nds32/Makefile
index b33d5d81b6ae..7be31e3d7f2d 100644
--- a/arch/nds32/Makefile
+++ b/arch/nds32/Makefile
@@ -27,8 +27,6 @@ export TEXTADDR
# If we have a machine-specific directory, then include it in the build.
-core-y += arch/nds32/kernel/ arch/nds32/mm/
-core-$(CONFIG_FPU) += arch/nds32/math-emu/
libs-y += arch/nds32/lib/
ifdef CONFIG_CPU_LITTLE_ENDIAN
@@ -44,7 +42,6 @@ CHECKFLAGS += -D__NDS32_EB__
endif
boot := arch/nds32/boot
-core-y += $(boot)/dts/
Image: vmlinux
$(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
--
2.32.0
next reply other threads:[~2022-02-14 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 3:37 Masahiro Yamada [this message]
2022-02-14 3:39 ` [PATCH] nds32: move core-y in arch/nds32/Makefile to arch/nds32/Kbuild Masahiro Yamada
-- strict thread matches above, loose matches on Subject: below --
2021-08-11 16:44 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=20220214033724.2409951-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickhu@andestech.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 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).