From: Stefano Stabellini <sstabellini@kernel.org>
To: xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <stefanos@xilinx.com>,
sstabellini@kernel.org, andrii_anisov@epam.com,
julien.grall@linaro.org
Subject: [PATCH v2 5/6] xen/arm: make platform specific code dependent on ALL32_PLAT or ALL64_PLAT
Date: Thu, 23 Aug 2018 16:33:39 -0700 [thread overview]
Message-ID: <1535067220-16825-5-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1808231631270.14449@sstabellini-ThinkPad-X260>
Compile platform code that doesn't have its own specific kconfig option
only if ALL32_PLAT or ALL64_PLAT depending on the architecture. The
benefit is that choosing one of the platforms available as a menu
option allows the user not to build other unnecessary platform code.
Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
---
xen/arch/arm/platforms/Makefile | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/xen/arch/arm/platforms/Makefile b/xen/arch/arm/platforms/Makefile
index 190a744..daf0d45 100644
--- a/xen/arch/arm/platforms/Makefile
+++ b/xen/arch/arm/platforms/Makefile
@@ -1,12 +1,12 @@
obj-y += vexpress.o
-obj-$(CONFIG_ARM_32) += brcm.o
-obj-$(CONFIG_ARM_32) += exynos5.o
-obj-$(CONFIG_ARM_32) += midway.o
+obj-$(CONFIG_ALL32_PLAT) += brcm.o
+obj-$(CONFIG_ALL32_PLAT) += exynos5.o
+obj-$(CONFIG_ALL32_PLAT) += midway.o
obj-$(CONFIG_OMAP5_PLATFORM) += omap5.o
obj-$(CONFIG_RCAR2_PLATFORM) += rcar2.o
-obj-$(CONFIG_ARM_64) += seattle.o
+obj-$(CONFIG_ALL64_PLAT) += seattle.o
obj-$(CONFIG_SUNXI_PLATFORM) += sunxi.o
-obj-$(CONFIG_ARM_64) += thunderx.o
+obj-$(CONFIG_ALL64_PLAT) += thunderx.o
obj-$(CONFIG_THUNDERX_PLATFORM) += thunderx.o
-obj-$(CONFIG_ARM_64) += xgene-storm.o
-obj-$(CONFIG_MPSOC_PLATFORM) += xilinx-zynqmp.o
+obj-$(CONFIG_ALL64_PLAT) += xgene-storm.o
+obj-$(CONFIG_MPSOC_PLATFORM) += xilinx-zynqmp.o
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-08-23 23:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 23:33 [PATCH v2 00/10] arm: add one kconfig option per platform Stefano Stabellini
2018-08-23 23:33 ` [PATCH v2 1/6] xen/arm: add THUNDERX kconfig Stefano Stabellini
2018-08-24 8:33 ` Julien Grall
2018-08-23 23:33 ` [PATCH v2 2/6] xen/arm: add SUNXI kconfig Stefano Stabellini
2018-08-23 23:33 ` [PATCH v2 3/6] xen/arm: add RCAR2 kconfig Stefano Stabellini
2018-08-24 8:38 ` Julien Grall
2018-08-24 19:31 ` Stefano Stabellini
2018-08-28 14:45 ` Julien Grall
2018-08-30 19:06 ` Stefano Stabellini
2018-08-23 23:33 ` [PATCH v2 4/6] xen/arm: add OMAP5 kconfig Stefano Stabellini
2018-08-23 23:33 ` Stefano Stabellini [this message]
2018-08-23 23:33 ` [PATCH v2 6/6] xen/arm: introduce NO_PLAT Stefano Stabellini
2018-08-24 8:35 ` Julien Grall
2018-08-24 19:33 ` Stefano Stabellini
2018-08-24 8:22 ` [PATCH v2 00/10] arm: add one kconfig option per platform Julien Grall
2018-08-24 19:38 ` Stefano Stabellini
2018-08-28 16:44 ` Julien Grall
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=1535067220-16825-5-git-send-email-sstabellini@kernel.org \
--to=sstabellini@kernel.org \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@linaro.org \
--cc=stefanos@xilinx.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).