All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Dan Murphy <dmurphy@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [PATCH] optee-os: Update OPTEE OS tag to 3.5.0-rc1 and ti2019.01-rc1
Date: Tue, 23 Apr 2019 17:58:21 -0400	[thread overview]
Message-ID: <20190423215821.GD6705@beryl> (raw)
In-Reply-To: <f3b645a0-4d38-58e2-b92c-13cf3ab41970@ti.com>

On Tue, Apr 23, 2019 at 04:47:05PM -0500, Dan Murphy wrote:
> Denys
> 
> On 4/23/19 4:45 PM, Denys Dmytriyenko wrote:
> > ERROR: QA Issue: optee-os: The LIC_FILES_CHKSUM does not match for file://.../optee-os/3.4.0+gitAUTOINC+b38f935200-r0.arago1/git/LICENSE;md5=69663ab153298557a59c67a60a743e5b
> > optee-os: Check if the license information has changed in .../optee-os/3.4.0+gitAUTOINC+b38f935200-r0.arago1/git/LICENSE to verify that the LICENSE value "BSD" remains valid [license-checksum]
> > 
> 
> Is this a version mismatch then?  Andrew said this was 3.5.0-rc1 but it 
> appears that this is not what is in the os code.
> 
> Maybe the PV should be 
> 
> PV = "3.4.0+git${SRCPV}"

Yes, it was already 3.4.0 in thud - looks like you used the old branch as a 
base for your patch...


> Dan
> 
> > 
> > On Tue, Apr 23, 2019 at 01:54:24PM -0500, Dan Murphy wrote:
> >> Andrew
> >>
> >> On 4/23/19 1:52 PM, Andrew F. Davis wrote:
> >>> On 4/23/19 2:40 PM, Dan Murphy wrote:
> >>>> +Andrew
> >>>>
> >>>> On 4/23/19 1:38 PM, Dan Murphy wrote:
> >>>>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> >>>>> ---
> >>>>>  .../recipes-security/optee/optee-os_git.bbappend              | 4 ++--
> >>>>>  1 file changed, 2 insertions(+), 2 deletions(-)
> >>>>>
> >>>>> diff --git a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend b/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend
> >>>>> index 2204a50c..ee87b3c7 100644
> >>>>> --- a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend
> >>>>> +++ b/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend
> >>>>> @@ -2,7 +2,7 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> >>>>>  
> >>>>>  PR_append = ".arago0"
> >>>>>  
> >>>>> -PV = "3.2.0+git${SRCPV}"
> >>>>> +PV = "3.5.0+git${SRCPV}"
> >>>
> >>> Might want to do the same for client/test, but they got tagged at 3.4.0,
> >>> I've moved the HEAD forward to 3.5.0, we can wait till then next rc tag
> >>> to move them here, it should not be a problem.
> >>>
> >>
> >> Yeah rc1 was not tagged with these so rc2 we will update them
> >>
> >> Dan
> >>
> >>> Andrew
> >>>
> >>>>>  
> >>>>>  is_armv7 = "1"
> >>>>>  is_armv7_aarch64 = "0"
> >>>>> @@ -11,7 +11,7 @@ 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 = "48952f9f76d885df4cb65f8479a4cf7dedf0ee54"
> >>>>> +SRCREV = "b38f935200f67f9408d7c5d99fe703e5cc806c65"
> >>>>>  
> >>>>>  ARMCORE = "CFG_ARM32_core=y ta-targets=ta_arm32"
> >>>>>  ARMCORE_aarch64 = "CFG_ARM64_core=y ta-targets=ta_arm64"
> >>>>>


  reply	other threads:[~2019-04-23 21:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 18:38 [PATCH] optee-os: Update OPTEE OS tag to 3.5.0-rc1 and ti2019.01-rc1 Dan Murphy
2019-04-23 18:40 ` Dan Murphy
2019-04-23 18:52   ` Andrew F. Davis
2019-04-23 18:54     ` Dan Murphy
2019-04-23 21:45       ` Denys Dmytriyenko
2019-04-23 21:47         ` Dan Murphy
2019-04-23 21:58           ` Denys Dmytriyenko [this message]
2019-04-24  0:07             ` Dan Murphy
2019-04-23 21:49         ` Andrew F. Davis
2019-04-23 21:55           ` Denys Dmytriyenko
2019-04-29 18:13     ` Denys Dmytriyenko
2019-04-29 20:13       ` Andrew F. Davis
2019-04-29 20:15         ` Denys Dmytriyenko
2019-04-29 20:20           ` Andrew F. Davis

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=20190423215821.GD6705@beryl \
    --to=denys@ti.com \
    --cc=dmurphy@ti.com \
    --cc=meta-arago@arago-project.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.