Skip to contentSkip to conversation

optee-os: update SRCREV to pick latest

PATCH In review [email protected] 2 participants 4 messages Dec 7, 2020 – Dec 17, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 optee-os: update SRCREV to pick latest

From: Praneeth Bajjuri <[email protected]>

updating SRCREV to pick the latest commit on
repo: ti-optee-os.git
branch: ti-optee-os

---
 meta-arago-distro/recipes-security/optee/optee-os_git.bbappend | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +1 -1
index 677c6dd0..8a52833e 100644
@@ -4,4 +4,4 @@ SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \
            file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \
 "
 BRANCH = "ti-optee-os"
-SRCREV = "199fca17b575d4c748c9c435e908a6ec9618c75a"
+SRCREV = "f414104d552c8ab96ccc3c4182c395c20e3a0a34"
Signature · 1 line
2.17.1
#1 lore raw

Praneeth

Quoted 16 lines · On 12/4/20 3:47 PM, [email protected] wrote:

From: Praneeth Bajjuri <[email protected]>

updating SRCREV to pick the latest commit on
repo: ti-optee-os.git
branch: ti-optee-os

---
  meta-arago-distro/recipes-security/optee/optee-os_git.bbappend | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +0 -0
index 677c6dd0..8a52833e 100644

meta-arago-distro/recipes-security/optee/optee-os_git.bbappend SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \ · line 7

Quoted 5 lines
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +1 -1
@@ -4,4 +4,4 @@ SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \
             file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \
  "
  BRANCH = "ti-optee-os"
-SRCREV = "199fca17b575d4c748c9c435e908a6ec9618c75a"
+SRCREV = "f414104d552c8ab96ccc3c4182c395c20e3a0a34"

Are you updating this to a new version or reverting to an older version?  If so you probably want to add a PV = "3.xx" here.

meta-arm has the PV set to 3.8 unless you are moving to 3.8.

Since the git.ti.com repo does not contain the optee upstream tags it is difficult to know what version this is. (Yes I know you just picked up the maintenance).

Dan

#2 lore raw
Quoted 28 lines · Dan Murphy

Praneeth

Quoted 20 lines · On 12/4/20 3:47 PM, [email protected] wrote:

From: Praneeth Bajjuri <[email protected]>

updating SRCREV to pick the latest commit on
repo: ti-optee-os.git
branch: ti-optee-os

---
  meta-arago-distro/recipes-security/optee/optee-os_git.bbappend | 2 +-

  1 file changed, 1 insertion(+), 1 deletion(-)
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +0 -0
index 677c6dd0..8a52833e 100644
@@ -4,4 +4,4 @@ SRC_URI = 
 "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \
              file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \

  "
  BRANCH = "ti-optee-os"

meta-arago-distro/recipes-security/optee/optee-os_git.bbappend SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \ · line 7

Quoted 2 lines
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +1 -1
-SRCREV = "199fca17b575d4c748c9c435e908a6ec9618c75a"
+SRCREV = "f414104d552c8ab96ccc3c4182c395c20e3a0a34"

Are you updating this to a new version or reverting to an older version?  If so you probably want to add a PV = "3.xx" here.

Quoted 1 line

meta-arm has the PV set to 3.8 unless you are moving to 3.8.

There is no change in OPTEE version between those commit sha.

Quoted 2 lines

Since the git.ti.com repo does not contain the optee upstream tags it is difficult to know what version this is. (Yes I know you just picked up the maintenance).

Dan , Please go ahead and pull this update ( we will continue to be on 3.8)

Quoted 3 lines

Dan

#3 lore raw

Praneeth

Quoted 31 lines · Praneeth
Quoted 28 lines · Dan Murphy

Praneeth

Quoted 20 lines · On 12/4/20 3:47 PM, [email protected] wrote:

From: Praneeth Bajjuri <[email protected]>

updating SRCREV to pick the latest commit on
repo: ti-optee-os.git
branch: ti-optee-os

---
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend | 2 +-

  1 file changed, 1 insertion(+), 1 deletion(-)
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +0 -0
index 677c6dd0..8a52833e 100644
@@ -4,4 +4,4 @@ SRC_URI = 
 "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \
 file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \

  "
  BRANCH = "ti-optee-os"

meta-arago-distro/recipes-security/optee/optee-os_git.bbappend SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \ · line 7

Quoted 2 lines
meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +1 -1
-SRCREV = "199fca17b575d4c748c9c435e908a6ec9618c75a"
+SRCREV = "f414104d552c8ab96ccc3c4182c395c20e3a0a34"

Are you updating this to a new version or reverting to an older version?  If so you probably want to add a PV = "3.xx" here.

Quoted 8 lines
Quoted 1 line

meta-arm has the PV set to 3.8 unless you are moving to 3.8.

There is no change in OPTEE version between those commit sha.

Quoted 2 lines

Since the git.ti.com repo does not contain the optee upstream tags it is difficult to know what version this is. (Yes I know you just picked up the maintenance).

Dan , Please go ahead and pull this update ( we will continue to be on 3.8)

Thanks for the clarification.

I will apply it

Dan