From: Denys Dmytriyenko <denis@denix.org>
To: meta-ti@lists.yoctoproject.org
Cc: Denys Dmytriyenko <denys@konsulko.com>
Subject: Re: [meta-ti] [master][PATCH] optee-os: sync up with upstream meta-arm update
Date: Tue, 17 Jan 2023 15:24:42 -0500 [thread overview]
Message-ID: <20230117202442.GD22689@denix.org> (raw)
In-Reply-To: <1739A240EA9239F6.25137@lists.yoctoproject.org>
Ping. As master is now broken!
On Thu, Jan 12, 2023 at 06:12:12PM +0000, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@konsulko.com>
>
> Upstream meta-arm has updated optee-os to 3.19 and our local changes
> conflict with that. Update bbappend to match upstream.
>
> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
> ---
> meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend b/meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend
> index 8640d7b0..6f711101 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend
> +++ b/meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend
> @@ -1,12 +1,3 @@
> -PV:ti-soc = "3.19.0+git${SRCPV}"
> -SRCREV:ti-soc = "afacf356f9593a7f83cae9f96026824ec242ff52"
> -
> -# These patches are from upstream against v3.18, but we moved to v3.19 and the
> -# patches are now invalid. These can be removed once upstream moves up to or
> -# beyond v3.19.
> -SRC_URI:remove:ti-soc = "file://0008-no-warn-rwx-segments.patch"
> -SRC_URI:remove:ti-soc = "file://0009-add-z-execstack.patch"
> -
> EXTRA_OEMAKE:append:k3 = "${@ ' CFG_CONSOLE_UART='+ d.getVar('OPTEE_K3_USART') if d.getVar('OPTEE_K3_USART') else ''}"
>
> EXTRA_OEMAKE:append:am62xx = " CFG_WITH_SOFTWARE_PRNG=y CFG_TEE_CORE_LOG_LEVEL=1"
> --
> 2.25.1
parent reply other threads:[~2023-01-17 20:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1739A240EA9239F6.25137@lists.yoctoproject.org>]
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=20230117202442.GD22689@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-ti@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 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.