From: "Jon Mason" <jdmason@kudzu.us>
To: Usama Arif <usama.arif@arm.com>,
meta-arm@lists.yoctoproject.org, nd@arm.com,
Prabin CA <prabin.ca@rm.com>
Subject: Re: [meta-arm] [PATCH 1/2] meta-arm: trusted-firmware-a: add branch name for mbedtls
Date: Fri, 7 Aug 2020 16:59:21 -0400 [thread overview]
Message-ID: <20200807205920.GB440@kudzu.us> (raw)
In-Reply-To: <162917F004EE1F95.1838@lists.yoctoproject.org>
On Fri, Aug 07, 2020 at 04:57:39PM -0400, Jon Mason via lists.yoctoproject.org wrote:
> It appears that these do not apply cleanly to the master branch. I'm
> not sure if it is the SMTP issue or something else. Can you please
> rebase and resend?
Disregard, I see the new versions now.
Thanks,
Jon
>
> Thanks,
> Jon
>
>
> On Wed, Aug 05, 2020 at 11:16:28AM +0100, Usama Arif wrote:
> > It appears that the mbedtls team have moved the SHA which
> > meta-arm was using from master branch. It is still present
> > in mbedtls-2.18 branch so this is now used.
> >
> > Change-Id: Ie932f446067767e85a25583b1bdc02b4739e323f
> > Signed-off-by: Usama Arif <usama.arif@arm.com>
> > Signed-off-by: Prabin CA <prabin.ca@rm.com>
> > ---
> > .../recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.3.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.3.bb b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.3.bb
> > index 8286b64..7279173 100644
> > --- a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.3.bb
> > +++ b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.3.bb
> > @@ -21,7 +21,7 @@ LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89
> > # Those are used in trusted-firmware-a.inc if TFA_MBEDTLS is set to 1
> > #
> >
> > -SRC_URI_MBEDTLS = "git://github.com/ARMmbed/mbedtls.git;name=mbedtls;protocol=https;destsuffix=git/mbedtls"
> > +SRC_URI_MBEDTLS = "git://github.com/ARMmbed/mbedtls.git;name=mbedtls;protocol=https;destsuffix=git/mbedtls;branch=mbedtls-2.18"
> >
> > # mbed TLS v2.18.1
> > SRCREV_mbedtls = "ca933c7e0c9e84738b168b6b0feb89af4183a60a"
> > --
> > 2.17.1
> >
>
> >
>
>
prev parent reply other threads:[~2020-08-07 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 10:16 [PATCH 1/2] meta-arm: trusted-firmware-a: add branch name for mbedtls Usama Arif
2020-08-05 10:16 ` [PATCH 2/2] arm-bsp: trusted-firmware: tc0: remove SHA " Usama Arif
2020-08-07 20:57 ` [meta-arm] [PATCH 1/2] meta-arm: trusted-firmware-a: add branch name " Jon Mason
[not found] ` <162917F004EE1F95.1838@lists.yoctoproject.org>
2020-08-07 20:59 ` Jon Mason [this message]
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=20200807205920.GB440@kudzu.us \
--to=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.com \
--cc=prabin.ca@rm.com \
--cc=usama.arif@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 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.