From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] powerpc: fix arch/powerpc/dts/Makefile
Date: Thu, 14 Mar 2019 14:58:34 +0900 [thread overview]
Message-ID: <1552543116-21868-3-git-send-email-yamada.masahiro@socionext.com> (raw)
In-Reply-To: <1552543116-21868-1-git-send-email-yamada.masahiro@socionext.com>
Since commit 27cb7300ffda ("Ensure device tree DTS is compiled"),
build succeeds irrespective of the correctness of Makefile.
I am going to revert that commit, so wrong code must be fixed.
CONFIG_MCR3000 is not defined anywhere. CONFIG_TARGET_MCR3000 is the
correct one.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
---
arch/powerpc/dts/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/dts/Makefile b/arch/powerpc/dts/Makefile
index 172bed4..f080a96 100644
--- a/arch/powerpc/dts/Makefile
+++ b/arch/powerpc/dts/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0+
dtb-$(CONFIG_TARGET_T2080QDS) += t2080qds.dtb
-dtb-$(CONFIG_MCR3000) += mcr3000.dtb
+dtb-$(CONFIG_TARGET_MCR3000) += mcr3000.dtb
targets += $(dtb-y)
--
2.7.4
next prev parent reply other threads:[~2019-03-14 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 5:58 [U-Boot] [PATCH 0/4] Let's write correct arch/*/dts/Makefile Masahiro Yamada
2019-03-14 5:58 ` [U-Boot] [PATCH 1/4] ARM: fix arch/arm/dts/Makefile Masahiro Yamada
2019-03-14 6:26 ` Chris Packham
2019-03-22 23:17 ` [U-Boot] [U-Boot,1/4] " Tom Rini
2019-03-14 5:58 ` Masahiro Yamada [this message]
2019-03-22 23:17 ` [U-Boot] [U-Boot,2/4] powerpc: fix arch/powerpc/dts/Makefile Tom Rini
2019-03-14 5:58 ` [U-Boot] [PATCH 3/4] mips: add missing dtb-y to arch/mips/dts/Makefile Masahiro Yamada
2019-03-15 11:11 ` Daniel Schwierzeck
2019-03-22 23:18 ` [U-Boot] [U-Boot, " Tom Rini
2019-03-14 5:58 ` [U-Boot] [PATCH 4/4] Revert "Ensure device tree DTS is compiled" Masahiro Yamada
2019-03-22 23:18 ` [U-Boot] [U-Boot, " Tom Rini
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=1552543116-21868-3-git-send-email-yamada.masahiro@socionext.com \
--to=yamada.masahiro@socionext.com \
--cc=u-boot@lists.denx.de \
/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.