From: "Vincent Stehlé" <vincent.stehle@arm.com>
To: Bryan Brattlof <bb@ti.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/4] bump optee to 4.3.0
Date: Tue, 23 Jul 2024 15:31:48 +0200 [thread overview]
Message-ID: <Zp-wxDuSSLIA_yz8@debian> (raw)
In-Reply-To: <20240722-optee-bump-v1-0-8e25b342634d@ti.com>
On Mon, Jul 22, 2024 at 08:32:05PM -0500, Bryan Brattlof wrote:
> Hello everyone,
>
> This small series bumps all optee packages to 4.3.0 and updates their
> default hashes.
Hi Bryan,
Thanks for bumping; this works fine for me on top of master, commit 0d582054e131
("package/python-can/Config.in: sort selects").
- The OP-TEE unit test runs fine (tests.boot.test_optee_os).
- All EBBR configs build and run fine (arm_fvp_ebbr_defconfig,
qemu_aarch64_ebbr_defconfig, qemu_arm_ebbr_defconfig).
- The qemu_arm_vexpress_tz_defconfig, also using OP-TEE, builds and runs fine.
Tested-by: Vincent Stehlé <vincent.stehle@arm.com>
I could not test the other configs using OP-TEE (beagleboneai64_defconfig,
beagleplay_defconfig, ti_am62ax_sk_defconfig, ti_am62x_sk_defconfig,
ti_am64x_sk_defconfig) as they will not build for me even before this series.
Best regards,
Vincent.
>
> Happy reviewing
> ~Bryan
>
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
> Bryan Brattlof (4):
> boot/optee-os: bump to 4.3.0
> package/optee-client: bump to 4.3.0
> package/optee-examples: bump to 4.3.0
> package/optee-test: bump to 4.3.0
>
> boot/optee-os/Config.in | 4 ++--
> boot/optee-os/optee-os.hash | 4 ++--
> package/optee-client/optee-client.hash | 4 ++--
> package/optee-client/optee-client.mk | 2 +-
> package/optee-examples/optee-examples.hash | 4 ++--
> package/optee-examples/optee-examples.mk | 2 +-
> package/optee-test/optee-test.hash | 4 ++--
> package/optee-test/optee-test.mk | 2 +-
> 8 files changed, 13 insertions(+), 13 deletions(-)
> ---
> base-commit: 4e4554eeb76e8b516c6cbcd66f15868492aac594
> change-id: 20240722-optee-bump-1b173476a4f1
>
> Best regards,
> --
> Bryan Brattlof <bb@ti.com>
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-23 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 1:32 [Buildroot] [PATCH 0/4] bump optee to 4.3.0 Bryan Brattlof via buildroot
2024-07-23 1:32 ` [Buildroot] [PATCH 1/4] boot/optee-os: bump " Bryan Brattlof via buildroot
2024-07-23 1:32 ` [Buildroot] [PATCH 2/4] package/optee-client: " Bryan Brattlof via buildroot
2024-07-23 1:32 ` [Buildroot] [PATCH 3/4] package/optee-examples: " Bryan Brattlof via buildroot
2024-07-23 1:32 ` [Buildroot] [PATCH 4/4] package/optee-test: " Bryan Brattlof via buildroot
2024-07-23 8:51 ` [Buildroot] [PATCH 0/4] bump optee " Thomas Petazzoni via buildroot
2024-07-23 13:31 ` Vincent Stehlé [this message]
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=Zp-wxDuSSLIA_yz8@debian \
--to=vincent.stehle@arm.com \
--cc=bb@ti.com \
--cc=buildroot@buildroot.org \
/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.