From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 4/4] tests: add OP-TEE test suite
Date: Fri, 08 Nov 2019 15:51:21 +0100 [thread overview]
Message-ID: <1831162.TJXf6fBH3I@diego> (raw)
In-Reply-To: <20191023144641.5710-4-heiko@sntech.de>
Am Mittwoch, 23. Oktober 2019, 16:46:41 CET schrieb Heiko Stuebner:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> OP-TEE can get supplied with a devicetree and will then insert
> its firmware node and reserved-memory sections into it.
> As this devicetree often is not the one supplied to a later
> loaded kernel, a previous commit added functionality to transfer
> these nodes onto that new devicetree.
>
> To make sure this functionality stays intact, also add a test
> for the transfer functionality.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
this patch already received in v2 a
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2019-11-08 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 14:46 [U-Boot] [PATCH v3 1/4] fdtdec: protect against another NULL phandlep in fdtdec_add_reserved_memory() Heiko Stuebner
2019-10-23 14:46 ` [U-Boot] [PATCH v3 2/4] fdtdec: only create phandle if caller wants it " Heiko Stuebner
2019-11-08 14:51 ` Heiko Stübner
2019-11-14 13:42 ` sjg at google.com
2019-11-14 13:43 ` sjg at google.com
2019-10-23 14:46 ` [U-Boot] [PATCH v3 3/4] image: fdt: copy possible optee nodes to a loaded devicetree Heiko Stuebner
2019-11-14 13:43 ` Simon Glass
2019-10-23 14:46 ` [U-Boot] [PATCH v3 4/4] tests: add OP-TEE test suite Heiko Stuebner
2019-11-08 14:51 ` Heiko Stübner [this message]
2019-11-14 13:42 ` sjg at google.com
2019-11-14 13:43 ` sjg at google.com
2019-11-08 14:50 ` [U-Boot] [PATCH v3 1/4] fdtdec: protect against another NULL phandlep in fdtdec_add_reserved_memory() Heiko Stübner
2019-11-14 13:43 ` sjg at google.com
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=1831162.TJXf6fBH3I@diego \
--to=heiko@sntech.de \
--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