From: Jose Quaresma <quaresma.jose@gmail.com>
To: meta-arm@lists.yoctoproject.org
Cc: ricardo@foundries.io, Jose Quaresma <jose.quaresma@foundries.io>
Subject: [meta-arm][PATCH 1/3] optee-ftpm/optee-os: add missing space in EXTRA_OEMAKE
Date: Wed, 26 Oct 2022 14:18:52 +0000 [thread overview]
Message-ID: <20221026141854.1557213-1-jose.quaresma@foundries.io> (raw)
When append to variable a space is required at the beginning.
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
---
meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend b/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
index acea7502..40423615 100644
--- a/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
+++ b/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
@@ -7,7 +7,8 @@ DEPENDS:append = "\
'' , \
d)}"
-EXTRA_OEMAKE:append = "${@bb.utils.contains('MACHINE_FEATURES', \
+EXTRA_OEMAKE:append = "\
+ ${@bb.utils.contains('MACHINE_FEATURES', \
'optee-ftpm', \
'CFG_EARLY_TA=y EARLY_TA_PATHS="${STAGING_DIR_TARGET}/lib/optee_armtz/${FTPM_UUID}.stripped.elf"', \
'', \
--
2.34.1
next reply other threads:[~2022-10-26 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 14:18 Jose Quaresma [this message]
2022-10-26 14:18 ` [meta-arm][PATCH 2/3] optee-ftpm/optee-os: rewite in a way to be less error prone Jose Quaresma
2022-10-27 6:19 ` Mikko Rapeli
2022-10-27 9:01 ` Jose Quaresma
2022-10-27 14:03 ` Jon Mason
2022-10-27 14:26 ` Jose Quaresma
2022-10-26 14:18 ` [meta-arm][PATCH 3/3] optee-os-ts: avoid using escape chars in EXTRA_OEMAKE Jose Quaresma
2022-10-27 6:20 ` Mikko Rapeli
2022-10-27 14:06 ` Jon Mason
2022-10-27 6:18 ` [meta-arm][PATCH 1/3] optee-ftpm/optee-os: add missing space " Mikko Rapeli
2022-10-27 8:57 ` Jose Quaresma
2022-10-27 21:38 ` [PATCH " Jon Mason
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=20221026141854.1557213-1-jose.quaresma@foundries.io \
--to=quaresma.jose@gmail.com \
--cc=jose.quaresma@foundries.io \
--cc=meta-arm@lists.yoctoproject.org \
--cc=ricardo@foundries.io \
/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.