From: Denys Dmytriyenko <denis@denix.org>
To: s-joshi@ti.com
Cc: meta-ti@lists.yoctoproject.org, kamlesh@ti.com,
k-malarvizhi@ti.com, s-tripathi1@ti.com, praneeth@ti.com,
m-chawdhry@ti.com, vishalm@ti.com
Subject: Re: [meta-ti][master][PATCH] meta-ti: optee: Update to 4.10.0 tag
Date: Fri, 15 May 2026 10:50:51 -0400 [thread overview]
Message-ID: <20260515145051.GC7941@denix.org> (raw)
In-Reply-To: <20260515062818.1468076-1-s-joshi@ti.com>
Should this also go into wrynose besides master?
On Fri, May 15, 2026 at 11:58:18AM +0530, Suhaas Joshi via lists.yoctoproject.org wrote:
> Update optee_os, optee_test, optee_client, optee_examples and optee_ftpm to
> 4.10.0 tag.
>
> Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
> ---
> Tested this on AM62L using `xtest`.
> ---
> .../recipes-security/optee/optee-client-ti-version.inc | 2 +-
> .../recipes-security/optee/optee-examples-ti-version.inc | 2 +-
> meta-ti-bsp/recipes-security/optee/optee-ftpm-ti-version.inc | 2 +-
> meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc | 4 ++--
> meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc | 4 ++--
> 5 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc b/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc
> index 68b6b262..7968f3fb 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc
> @@ -1,2 +1,2 @@
> -PV = "4.9.0+git"
> +PV = "4.10.0+git"
> SRCREV = "9f5e90918093c1d1cd264d8149081b64ab7ba672"
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc b/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc
> index 6ec2a83d..eea7762f 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc
> @@ -1,2 +1,2 @@
> -PV = "4.9.0+git"
> +PV = "4.10.0+git"
> SRCREV = "934c7edb74a26e90f68024cf441073528444177f"
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-ftpm-ti-version.inc b/meta-ti-bsp/recipes-security/optee/optee-ftpm-ti-version.inc
> index 350eb9c9..b961c70f 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-ftpm-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-ftpm-ti-version.inc
> @@ -1,3 +1,3 @@
> -PV = "4.9.0+git"
> +PV = "4.10.0+git"
> OPTEE_TA_GIT_TAG = "${@'branch=master' if d.getVar('PV') == 'git' or d.getVar('PV').endswith('+git') else 'tag=%s;nobranch=1' % d.getVar('PV')}"
> SRCREV_optee-ta = "a09269b15de635e1816fe832e26adfbfb44c5455"
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc b/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc
> index db18c696..473c5282 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc
> @@ -1,2 +1,2 @@
> -PV = "4.9.0+git"
> -SRCREV = "f2a7ad0638aeff5243593b33cc56ad064cae7615"
> +PV = "4.10.0+git"
> +SRCREV = "753afbbee1682f5d16fd30e87b31058a4fd4f4b8"
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc b/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc
> index 15b43063..8a8e9ac8 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc
> @@ -1,4 +1,4 @@
> FILESEXTRAPATHS:prepend := "${THISDIR}/optee-test:"
>
> -PV = "4.9.0+git"
> -SRCREV = "b27648ea8472cceceb8dda368a965c709066f7aa"
> +PV = "4.10.0+git"
> +SRCREV = "88c93e87a5c172363ee986ded036a25cafcc9d2c"
> --
> 2.34.1
next prev parent reply other threads:[~2026-05-15 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 6:28 [meta-ti][master][PATCH] meta-ti: optee: Update to 4.10.0 tag Suhaas Joshi
2026-05-15 6:47 ` PRC Automation
2026-05-15 14:50 ` Denys Dmytriyenko [this message]
2026-05-15 15:09 ` Ryan Eatmon
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=20260515145051.GC7941@denix.org \
--to=denis@denix.org \
--cc=k-malarvizhi@ti.com \
--cc=kamlesh@ti.com \
--cc=m-chawdhry@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=s-joshi@ti.com \
--cc=s-tripathi1@ti.com \
--cc=vishalm@ti.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 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.