From: Henning Schild <henning.schild@siemens.com>
To: baocheng_su@163.com
Cc: isar-users@googlegroups.com, jan.kiszka@siemens.com,
felix.moessbauer@siemens.com, christian.storm@siemens.com,
quirin.gylstorff@siemens.com, baocheng.su@siemens.com
Subject: Re: [PATCH v2 1/7] stm32mp15x: Bump optee-os to 3.21.0
Date: Thu, 22 Jun 2023 19:50:50 +0200 [thread overview]
Message-ID: <20230622195050.56758df7@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230621192217.2045717-2-baocheng_su@163.com>
Am Thu, 22 Jun 2023 03:22:11 +0800
schrieb baocheng_su@163.com:
> From: Baocheng Su <baocheng.su@siemens.com>
>
> Signed-off-by: Baocheng Su <baocheng.su@siemens.com>
> ---
> ...-os-stm32mp15x_3.11.0.bb => optee-os-stm32mp15x_3.21.0.bb} | 4
> ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta-isar/recipes-bsp/optee-os/{optee-os-stm32mp15x_3.11.0.bb
> => optee-os-stm32mp15x_3.21.0.bb} (81%)
>
> diff --git
> a/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb
> b/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.21.0.bb
> similarity index 81% rename from
> meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb rename
> to meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.21.0.bb index
> 08676be..b605149 100644 ---
> a/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb +++
> b/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.21.0.bb @@
> -6,11 +6,11 @@ require recipes-bsp/optee-os/optee-os-custom.inc
> SRC_URI += "https://github.com/OP-TEE/optee_os/archive/${PV}.tar.gz"
> -SRC_URI[sha256sum] =
> "3c34eda1052fbb9ed36fcfdfaecfd2685023b9290670c1a5982f8a0457bfd2cb"
> +SRC_URI[sha256sum] =
> "92a16e841b0bdb4bfcb1c20b6a1bd3309092203d534ed167dfdb5a5f395bf60b" S
> = "${WORKDIR}/optee_os-${PV}"
> -DEBIAN_BUILD_DEPENDS += ", device-tree-compiler"
> +DEBIAN_BUILD_DEPENDS += ", device-tree-compiler,
> python3-cryptography:native"
> OPTEE_PLATFORM = "stm32mp1"
> OPTEE_EXTRA_BUILDARGS = " \
consider updating the Copyright header from 2020 to 2020-2023 in case
there will be another version of these patches
Henning
next prev parent reply other threads:[~2023-06-22 17:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 19:22 [PATCH v2 0/7] Add optee family and friends baocheng_su
2023-06-21 19:22 ` [PATCH v2 1/7] stm32mp15x: Bump optee-os to 3.21.0 baocheng_su
2023-06-22 17:50 ` Henning Schild [this message]
2023-06-21 19:22 ` [PATCH v2 2/7] Add recipe for optee TA devkit baocheng_su
2023-06-21 19:22 ` [PATCH v2 3/7] Add recipe for optee-client baocheng_su
2023-06-22 5:52 ` Jan Kiszka
2023-06-22 18:00 ` Henning Schild
2023-06-22 18:36 ` Jan Kiszka
2023-06-22 18:43 ` Henning Schild
2023-06-22 20:10 ` Jan Kiszka
2023-06-22 18:02 ` Henning Schild
2023-06-22 18:34 ` Jan Kiszka
2023-06-21 19:22 ` [PATCH v2 4/7] Add recipe for optee examples baocheng_su
2023-06-21 19:22 ` [PATCH v2 5/7] Add recipe for optee ftpm baocheng_su
2023-06-22 6:02 ` Jan Kiszka
2023-06-22 6:21 ` Su Baocheng
2023-06-22 6:40 ` Jan Kiszka
2023-06-21 19:22 ` [PATCH v2 6/7] initramfs: Add recipe for tee-supplicant hook baocheng_su
2023-06-21 19:22 ` [PATCH v2 7/7] initramfs: Add recipe for tee-ftpm hook baocheng_su
2023-06-22 6:01 ` [PATCH v2 0/7] Add optee family and friends Jan Kiszka
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=20230622195050.56758df7@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=baocheng_su@163.com \
--cc=christian.storm@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@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