mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: linux-arm-kernel@lists.infradead.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Tom Rini <trini@konsulko.com>,
	lkml <linux-kernel@vger.kernel.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Simon Glass <sjg@chromium.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: [PATCH v7 1/2] arm64: Add BOOT_TARGETS variable
Date: Wed, 29 Nov 2023 10:21:52 -0700	[thread overview]
Message-ID: <20231129172200.430674-2-sjg@chromium.org> (raw)
In-Reply-To: <20231129172200.430674-1-sjg@chromium.org>

Add a new variable containing a list of possible targets. Mark them as
phony. This matches the approach taken for arch/arm

Signed-off-by: Simon Glass <sjg@chromium.org>
---

Changes in v7:
- Drop the kbuild tag

Changes in v6:
- Drop the unwanted .gz suffix

 arch/arm64/Makefile | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
index 9a2d3723cd0f..1bd4fae6e806 100644
--- a/arch/arm64/Makefile
+++ b/arch/arm64/Makefile
@@ -150,6 +150,10 @@ libs-$(CONFIG_EFI_STUB) += $(objtree)/drivers/firmware/efi/libstub/lib.a
 # Default target when executing plain make
 boot		:= arch/arm64/boot
 
+BOOT_TARGETS	:= Image vmlinuz.efi
+
+PHONY += $(BOOT_TARGETS)
+
 ifeq ($(CONFIG_EFI_ZBOOT),)
 KBUILD_IMAGE	:= $(boot)/Image.gz
 else
@@ -159,7 +163,7 @@ endif
 all:	$(notdir $(KBUILD_IMAGE))
 
 vmlinuz.efi: Image
-Image vmlinuz.efi: vmlinux
+$(BOOT_TARGETS): vmlinux
 	$(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
 
 Image.%: Image
-- 
2.43.0.rc2.451.g8631bc7472-goog


  reply	other threads:[~2023-11-29 17:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 17:21 [PATCH v7 0/2] arm64: Add a build target for Flat Image Tree Simon Glass
2023-11-29 17:21 ` Simon Glass [this message]
2023-11-29 17:21 ` [PATCH v7 2/2] arm64: boot: Support " Simon Glass
2023-11-29 18:35   ` Ahmad Fatoum
2023-11-29 19:00     ` Simon Glass
2023-11-29 20:35       ` Ahmad Fatoum
2023-11-30 20:30     ` Simon Glass
2023-11-29 18:59   ` Ahmad Fatoum
2023-11-29 19:02     ` Tom Rini
2023-11-29 19:16       ` Ahmad Fatoum
2023-11-29 20:10         ` Tom Rini
2023-11-29 19:02     ` Simon Glass
2023-11-29 19:14       ` Ahmad Fatoum
2023-11-29 19:27         ` Simon Glass
2023-11-29 19:33           ` Ahmad Fatoum
2023-11-29 19:44             ` Simon Glass
2023-11-29 19:53               ` Ahmad Fatoum
2023-11-30 20:30                 ` Simon Glass
2023-12-01  2:03                   ` Ahmad Fatoum
2023-12-02 16:36                     ` Simon Glass
2023-12-04 17:52                       ` Doug Anderson
2023-12-05 11:15                         ` Ahmad Fatoum
2023-12-05 17:06                           ` Doug Anderson
2023-11-30  8:20   ` Nicolas Schier
2023-11-30 15:12     ` Masahiro Yamada
2023-11-30 15:38   ` Masahiro Yamada
2023-11-30 20:32     ` Simon Glass

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=20231129172200.430674-2-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=will@kernel.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®