From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 2/2] optee-ftpm-stm32mp15x: Switch to optee-ftpm class
Date: Fri, 12 Dec 2025 21:00:01 +0100 [thread overview]
Message-ID: <a9214f0b-94d7-4a3c-ae1a-7357fce00e4a@siemens.com> (raw)
In-Reply-To: <168e42a3-0671-493d-a41f-b8975d519105@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../optee-ftpm/optee-ftpm-stm32mp15x_0~230316+git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-isar/recipes-bsp/optee-ftpm/optee-ftpm-stm32mp15x_0~230316+git.bb b/meta-isar/recipes-bsp/optee-ftpm/optee-ftpm-stm32mp15x_0~230316+git.bb
index 53e2827c..215273c5 100644
--- a/meta-isar/recipes-bsp/optee-ftpm/optee-ftpm-stm32mp15x_0~230316+git.bb
+++ b/meta-isar/recipes-bsp/optee-ftpm/optee-ftpm-stm32mp15x_0~230316+git.bb
@@ -6,7 +6,7 @@
# SPDX-License-Identifier: MIT
#
-require recipes-bsp/optee-ftpm/optee-ftpm.inc
+inherit optee-ftpm
SRC_URI += " \
https://github.com/Microsoft/ms-tpm-20-ref/archive/${SRCREV}.tar.gz \
--
2.51.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/a9214f0b-94d7-4a3c-ae1a-7357fce00e4a%40siemens.com.
next prev parent reply other threads:[~2025-12-12 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 19:59 [PATCH 1/2] optee-ftpm: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-12-12 20:00 ` 'Jan Kiszka' via isar-users [this message]
2025-12-12 20:03 ` [PATCH 3/2] RECIPE-API-CHANGELOG: Add optee-ftpm conversion 'Jan Kiszka' via isar-users
2025-12-17 7:05 ` [PATCH 1/2] optee-ftpm: Migrate to a bbclass Anton Mikanovich
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=a9214f0b-94d7-4a3c-ae1a-7357fce00e4a@siemens.com \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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