From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] Use github mirrors for trusted-firmware-a
Date: Thu, 13 Jun 2024 13:20:18 +0300 [thread overview]
Message-ID: <f5b3cbf7356baa0dd5b99db404924b9bce796681.camel@ilbers.de> (raw)
In-Reply-To: <20240610102502.26267-1-ubely@ilbers.de>
On Mon, 2024-06-10 at 13:25 +0300, Uladzimir Bely wrote:
> Original repo from git.trustedfirmware.org appears to be down often,
> so readonly github mirror should work better.
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> .../trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb | 2
> +-
> .../trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb | 2
> +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-
> firmware-a-beagleplay_2.10.bb b/meta-isar/recipes-bsp/trusted-
> firmware-a/trusted-firmware-a-beagleplay_2.10.bb
> index aae3e2a8..bf1e3f05 100644
> --- a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-
> beagleplay_2.10.bb
> +++ b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-
> beagleplay_2.10.bb
> @@ -5,7 +5,7 @@
>
> require recipes-bsp/trusted-firmware-a/trusted-firmware-a-custom.inc
>
> -SRC_URI += "git://git.trustedfirmware.org/TF-A/trusted-firmware-
> a.git;protocol=https;branch=master"
> +SRC_URI += "git://github.com/ARM-software/arm-trusted-
> firmware.git;protocol=https;branch=master"
> SRCREV = "b6c0948400594e3cc4dbb5a4ef04b815d2675808"
>
> S = "${WORKDIR}/git"
> diff --git a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-
> firmware-a-stm32mp15x_2.4.bb b/meta-isar/recipes-bsp/trusted-
> firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb
> index cc2c2614..9927b460 100644
> --- a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-
> stm32mp15x_2.4.bb
> +++ b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-
> stm32mp15x_2.4.bb
> @@ -5,7 +5,7 @@
>
> require recipes-bsp/trusted-firmware-a/trusted-firmware-a-custom.inc
>
> -SRC_URI += "git://git.trustedfirmware.org/TF-A/trusted-firmware-
> a.git;protocol=https;branch=master"
> +SRC_URI += "git://github.com/ARM-software/arm-trusted-
> firmware.git;protocol=https;branch=master"
> SRCREV = "e2c509a39c6cc4dda8734e6509cdbe6e3603cdfc"
>
> S = "${WORKDIR}/git"
> --
> 2.44.2
>
Applied to next.
--
Best regards,
Uladzimir.
prev parent reply other threads:[~2024-06-13 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 10:25 Uladzimir Bely
2024-06-13 10:20 ` Uladzimir Bely [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=f5b3cbf7356baa0dd5b99db404924b9bce796681.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.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