From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v4 00/11] Support for building TF-A and OP-TEE, add STM32MP15x board
Date: Tue, 24 Nov 2020 17:52:35 +0100 [thread overview]
Message-ID: <20201124165235.GQ31950@yssyq.m.ilbers.de> (raw)
In-Reply-To: <cover.1606118039.git.jan.kiszka@siemens.com>
On Mon, Nov 23, 2020 at 08:53:48AM +0100, Jan Kiszka wrote:
> Changes in v4:
> - fix up OP-TEE version reporting for STM32MP15x
> - update to TF-A 2.4 and OP-TEE 3.11.0
Looks good to me, has just failed on CI due to python3. I'll test on top of the
python3 fix and let you know.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-11-24 16:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 7:53 Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 01/11] meta-isar: Lift de0-nano-soc build to buster Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 02/11] meta-isar: linux-mainline: Update to latest 5.4.70 Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 03/11] meta-isar: u-boot: Update to 2020.10 Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 04/11] meta-isar: u-boot: Factor our de0-nano-soc recipe Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 05/11] meta-isar: example-raw: Purge securetty from target image Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 06/11] Add STM32MP15x eval board Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 07/11] Add recipe include for building custom Trusted Firmware A Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 08/11] stm32mp15x: Switch to TF-A based boot Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 09/11] Add recipe include for building custom OP-TEE Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 10/11] meta-isar: u-boot-stm32mp15x: Add patches needed for OP-TEE usage Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 11/11] meta-isar: Add OP-TEE to STM32MP15x board Jan Kiszka
2020-11-24 16:52 ` Baurzhan Ismagulov [this message]
2020-11-25 5:47 ` [PATCH v4 00/11] Support for building TF-A and OP-TEE, add " Jan Kiszka
2020-11-25 18:58 ` Baurzhan Ismagulov
2020-11-25 20:30 ` Jan Kiszka
2020-11-26 15:54 ` 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=20201124165235.GQ31950@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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