From: Brian Sune <briansune@gmail.com>
To: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Cc: Tien Fong Chee <tien.fong.chee@altera.com>,
Brian Sune <briansune@gmail.com>
Subject: [PATCH v1] fix socfpga GEN5 handoff script path
Date: Mon, 19 Jan 2026 09:55:22 +0800 [thread overview]
Message-ID: <20260119015522.30558-1-briansune@gmail.com> (raw)
src variables not longer defined, fixed by srctree
Signed-off-by: Brian Sune <briansune@gmail.com>
---
arch/arm/mach-socfpga/config.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-socfpga/config.mk b/arch/arm/mach-socfpga/config.mk
index 2290118f747..3909d399895 100644
--- a/arch/arm/mach-socfpga/config.mk
+++ b/arch/arm/mach-socfpga/config.mk
@@ -23,7 +23,7 @@ socfpga_g5_handoff_prepare:
if [ -z "$$VENDOR" ] || [ -z "$$BOARD" ]; then \
exit 0; \
fi; \
- BOARD_DIR=$(src)/board/$$VENDOR/$$BOARD; \
+ BOARD_DIR=$(srctree)/board/$$VENDOR/$$BOARD; \
if [ "$$HANDOFF_PATH" ]; then \
echo "[INFO] Using manually specified handoff folder: $$HANDOFF_PATH"; \
else \
@@ -44,5 +44,5 @@ socfpga_g5_handoff_prepare:
fi; \
echo "[INFO] Found hiof file: $$HIOF_FILE"; \
echo "[INFO] Running BSP generator..."; \
- python3 $(src)/tools/cv_bsp_generator/cv_bsp_generator.py -i "$$HANDOFF_PATH" -o "$$BOARD_DIR/qts" || echo "[WARN] BSP generator failed, continuing..."; \
+ python3 $(srctree)/tools/cv_bsp_generator/cv_bsp_generator.py -i "$$HANDOFF_PATH" -o "$$BOARD_DIR/qts" || echo "[WARN] BSP generator failed, continuing..."; \
echo "[DONE] SoCFPGA QTS handoff conversion complete."
--
2.34.1
next reply other threads:[~2026-01-19 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 1:55 Brian Sune [this message]
2026-01-28 8:08 ` [PATCH v1] fix socfpga GEN5 handoff script path Chee, Tien Fong
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=20260119015522.30558-1-briansune@gmail.com \
--to=briansune@gmail.com \
--cc=tien.fong.chee@altera.com \
--cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox