From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, ali.oezaslan@arm.com
Subject: Re: [PATCH 0/3] arm-bsp/trusted-firmware-m:corstone1000: update to 2.0
Date: Mon, 18 Mar 2024 14:25:31 -0400 [thread overview]
Message-ID: <171078633825.3024366.8179804396643460340.b4-ty@arm.com> (raw)
In-Reply-To: <20240313201325.27043-1-ali.oezaslan@arm.com>
On Wed, 13 Mar 2024 20:13:22 +0000, ali.oezaslan@arm.com wrote:
> From: Ali Can Ozaslan <ali.oezaslan@arm.com>
>
> This change upgrades the trusted-firmware-m version to 2.0
> for Corstone-1000. Due to the changes in TF-M 2.0,
> psa services requires a seperate client_id.
> GNU Arm compiler version is bumped in tusted-firmware-m.
>
> [...]
Applied, thanks!
[1/3] arm-bsp/trusted-firmware-m: corstone1000: update to 2.0
commit: a8f47e9504a8319c635f0585d75df1737266c81b
[2/3] arm-bsp/trusted-services: corstone1000: Client Id adjustments after TF-M 2.0
commit: de57703654dc082fc75beac4060b941823619334
[3/3] arm/trusted-firmware-m: Change GNU Arm compiler version for TF-M 2.0
commit: ab6e5f47889803d4f8bd05bfe71fa20e0b7cd208
Best regards,
--
Jon Mason <jon.mason@arm.com>
prev parent reply other threads:[~2024-03-18 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:13 [PATCH 0/3] arm-bsp/trusted-firmware-m:corstone1000: update to 2.0 ali.oezaslan
2024-03-13 20:13 ` [PATCH 1/3] arm-bsp/trusted-firmware-m: corstone1000: " ali.oezaslan
2024-03-13 20:13 ` [PATCH 2/3] arm-bsp/trusted-services: corstone1000: Client Id adjustments after TF-M 2.0 ali.oezaslan
2024-03-13 20:13 ` [PATCH 3/3] arm/trusted-firmware-m: Change GNU Arm compiler version for " ali.oezaslan
2024-03-18 18:25 ` Jon Mason [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=171078633825.3024366.8179804396643460340.b4-ty@arm.com \
--to=jdmason@kudzu.us \
--cc=ali.oezaslan@arm.com \
--cc=meta-arm@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).