From: Jon Mason <jon.mason@arm.com>
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH 3/3] arm/hafnium: update to v2.10
Date: Mon, 4 Dec 2023 11:19:52 -0600 [thread overview]
Message-ID: <20231204171952.13471-3-jon.mason@arm.com> (raw)
In-Reply-To: <20231204171952.13471-1-jon.mason@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
---
.../recipes-bsp/hafnium/{hafnium_2.9.bb => hafnium_2.10.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-arm/recipes-bsp/hafnium/{hafnium_2.9.bb => hafnium_2.10.bb} (97%)
diff --git a/meta-arm/recipes-bsp/hafnium/hafnium_2.9.bb b/meta-arm/recipes-bsp/hafnium/hafnium_2.10.bb
similarity index 97%
rename from meta-arm/recipes-bsp/hafnium/hafnium_2.9.bb
rename to meta-arm/recipes-bsp/hafnium/hafnium_2.10.bb
index 0997448f..dea1bdcb 100644
--- a/meta-arm/recipes-bsp/hafnium/hafnium_2.9.bb
+++ b/meta-arm/recipes-bsp/hafnium/hafnium_2.10.bb
@@ -18,7 +18,7 @@ SRC_URI = "gitsm://git.trustedfirmware.org/hafnium/hafnium.git;protocol=https;br
file://0001-Use-pkg-config-native-to-find-the-libssl-headers.patch;patchdir=third_party/linux \
file://0001-work-around-visibility-issue.patch;patchdir=third_party/dtc \
"
-SRCREV = "0715b8e002cdfb92e6b7efb71128cb24557b70cb"
+SRCREV = "946fde92bedc95e1320684b0bc2dc752bc1e1bc7"
S = "${WORKDIR}/git"
B = "${WORKDIR}/build"
--
2.30.2
next prev parent reply other threads:[~2023-12-05 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 17:19 [PATCH 1/3] arm/trusted-firmware-a: move patch file to bbappend Jon Mason
2023-12-04 17:19 ` [PATCH 2/3] arm/trusted-firmware-a: update to 2.10 Jon Mason
2023-12-04 17:19 ` Jon Mason [this message]
2023-12-06 14:16 ` [PATCH 1/3] arm/trusted-firmware-a: move patch file to bbappend 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=20231204171952.13471-3-jon.mason@arm.com \
--to=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).