DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [DistroKit] [PATCH v2 5/7] firmware-imx: use foreach and ptx/nl
Date: Tue, 20 Jun 2023 15:29:29 +0200	[thread overview]
Message-ID: <20230620132931.2179983-6-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230620132931.2179983-1-m.olbrich@pengutronix.de>

Combining multiple commands with ';' hides errors. So use $(foreach ...)
and $(ptx/nl) to create separate commands that are executed individually
and all errors are caught.

Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
---
 configs/platform-v8a/rules/firmware-imx.make | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/configs/platform-v8a/rules/firmware-imx.make b/configs/platform-v8a/rules/firmware-imx.make
index 7bf1701b3ce1..56c8e24ecd69 100644
--- a/configs/platform-v8a/rules/firmware-imx.make
+++ b/configs/platform-v8a/rules/firmware-imx.make
@@ -59,11 +59,11 @@ ifdef PTXCONF_FIRMWARE_IMX_BOOTIMAGE_IMX8
 	@$(foreach f, lpddr4_pmu_train_1d_dmem.bin lpddr4_pmu_train_1d_imem.bin \
 	              lpddr4_pmu_train_2d_dmem.bin lpddr4_pmu_train_2d_imem.bin, \
 		install -v -D -m644 $(FIRMWARE_IMX_PKGDIR)/firmware/ddr/synopsys/$(f) \
-		$(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware/ddr/synopsys/$(f);)
+		$(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware/ddr/synopsys/$(f)$(ptx/nl))
 
 	@$(foreach f, signed_dp_imx8m.bin signed_hdmi_imx8m.bin, \
 		install -v -D -m644 $(FIRMWARE_IMX_PKGDIR)/firmware/hdmi/cadence/$(f) \
-		$(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware/hdmi/cadence/$(f);)
+		$(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware/hdmi/cadence/$(f)$(ptx/nl))
 endif
 
 	@$(call touch)
@@ -86,10 +86,10 @@ $(STATEDIR)/firmware-imx.targetinstall:
 	@$(call install_fixup, firmware-imx,SECTION,base)
 	@$(call install_fixup, firmware-imx,AUTHOR,"Philipp Zabel <p.zabel@pengutronix.de>")
 	@$(call install_fixup, firmware-imx,DESCRIPTION,missing)
-	@for f in $(FIRMWARE_IMX_INSTALL-y); do \
+	@$(foreach f,$(FIRMWARE_IMX_INSTALL-y), \
 		$(call install_copy, firmware-imx, 0, 0, 0644, \
-		$(FIRMWARE_IMX_PKGDIR)/firmware/vpu/$$f, /usr/lib/firmware/$$f); \
-	done
+			$(FIRMWARE_IMX_PKGDIR)/firmware/vpu/$(f), \
+			/usr/lib/firmware/$(f))$(ptx/nl))
 	@$(call install_finish, firmware-imx)
 
 	@$(call touch)
-- 
2.39.2




  parent reply	other threads:[~2023-06-20 13:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 13:29 [DistroKit] [PATCH v2 0/7] platform-v8a: cleanup firmware rules Michael Olbrich
2023-06-20 13:29 ` [DistroKit] [PATCH v2 1/7] platform-v8a: cleanup barebox firmware handling Michael Olbrich
2023-06-20 13:29 ` [DistroKit] [PATCH v2 2/7] firmware-imx: move to the correct section Michael Olbrich
2023-06-20 13:29 ` [DistroKit] [PATCH v2 3/7] platform-v8a: move platform menu files to platforms/ Michael Olbrich
2023-06-20 13:29 ` [DistroKit] [PATCH v2 4/7] platform-v8a: simplify dts search path Michael Olbrich
2023-06-20 13:29 ` Michael Olbrich [this message]
2023-06-20 13:29 ` [DistroKit] [PATCH v2 6/7] firmware-imx: make sure menuconfig works correctly Michael Olbrich
2023-06-20 13:29 ` [DistroKit] [PATCH v2 7/7] firmware-rockchip: " Michael Olbrich
2023-06-20 13:33 ` [DistroKit] [PATCH v2 0/7] platform-v8a: cleanup firmware rules Robert Schwebel

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=20230620132931.2179983-6-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=distrokit@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox