From: Ross Burton <Ross.Burton@arm.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Emekcan Aras <Emekcan.Aras@arm.com>,
"meta-arm@lists.yoctoproject.org"
<meta-arm@lists.yoctoproject.org>, Jon Mason <Jon.Mason@arm.com>,
nd <nd@arm.com>
Subject: Re: [meta-arm] [PATCH 2/5] arm/optee: support optee 3.19
Date: Thu, 12 Jan 2023 18:15:26 +0000 [thread overview]
Message-ID: <ECE5710C-8554-4807-941D-A4E6B0715A3E@arm.com> (raw)
In-Reply-To: <20230112175859.GZ22689@denix.org>
On 12 Jan 2023, at 17:58, Denys Dmytriyenko <denis@denix.org> wrote:
>
>> ---
>> diff --git a/meta-arm/recipes-security/optee/optee-os-3_19.inc b/meta-arm/recipes-security/optee/optee-os-3_19.inc
>> new file mode 100644
>> index 00000000..8adb6996
>> --- /dev/null
>> +++ b/meta-arm/recipes-security/optee/optee-os-3_19.inc
>
> While not critical, why does this inc file has "3_19" version in the name?
>
>
>> @@ -0,0 +1,82 @@
>> +SUMMARY = "OP-TEE Trusted OS"
>> +DESCRIPTION = "Open Portable Trusted Execution Environment - Trusted side of the TEE"
>> +HOMEPAGE = "https://www.op-tee.org/"
>> +
>> +LICENSE = "BSD-2-Clause"
>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=c1f21c4f72f372ef38a5a4aee55ec173"
>> +
>> +inherit deploy python3native
>> +require optee.inc
>> +
>> +FILESEXTRAPATHS:prepend := "${THISDIR}/optee-os-3_19:"
>
> Now, this is critical - why is there "3_19" version in the directory name?
Sorry, these were picked up in internal review but the series accidentally got merged. Hopefully Emekcan will be sending fixes shortly.
Ross
next prev parent reply other threads:[~2023-01-12 18:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 14:39 [PATCH 0/5] Add optee-os 3.19 recipe emekcan.aras
2022-12-21 14:39 ` [PATCH 1/5] arm/optee: Move optee-3.18 patches emekcan.aras
2022-12-21 14:39 ` [PATCH 2/5] arm/optee: support optee 3.19 emekcan.aras
2023-01-05 15:30 ` Ross Burton
2023-01-10 16:37 ` Jon Mason
2023-01-11 9:22 ` Emekcan Aras
2023-01-12 17:58 ` [meta-arm] " Denys Dmytriyenko
2023-01-12 18:15 ` Ross Burton [this message]
2023-01-13 9:52 ` Emekcan Aras
2023-01-13 10:38 ` Ross Burton
2022-12-21 14:39 ` [PATCH 3/5] arm-bsp/optee-os: Adds 3.19 bbappend emekcan.aras
2022-12-21 14:39 ` [PATCH 4/5] arm-bsp/optee-os: N1SDP support for optee-os 3.19 emekcan.aras
2022-12-21 14:39 ` [PATCH 5/5] arm/qemuarm-secureboot: pin optee-os version emekcan.aras
2022-12-21 15:37 ` [meta-arm] " Sumit Garg
2022-12-21 15:59 ` Emekcan Aras
2022-12-22 6:48 ` Sumit Garg
2022-12-22 8:42 ` Emekcan Aras
2022-12-23 5:47 ` Sumit Garg
2023-01-05 15:31 ` Ross Burton
2023-01-09 16:23 ` [PATCH 0/5] Add optee-os 3.19 recipe Jon Mason
2023-01-10 18:27 ` Jon Mason
2023-01-13 18:05 ` Jon Mason
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=ECE5710C-8554-4807-941D-A4E6B0715A3E@arm.com \
--to=ross.burton@arm.com \
--cc=Emekcan.Aras@arm.com \
--cc=Jon.Mason@arm.com \
--cc=denis@denix.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.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 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 NNTP newsgroup(s).