From: Jon Mason <jon.mason@arm.com>
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH 4/4] arm/execstack: correct broken version
Date: Fri, 18 Apr 2025 09:12:22 -0400 [thread overview]
Message-ID: <20250418131222.95241-4-jon.mason@arm.com> (raw)
In-Reply-To: <20250418131222.95241-1-jon.mason@arm.com>
`devtool check-upgrade-status` reports the new version as "20151030.",
which is the last tagged release. Given that there are a number of
commits since that tag and the tree doesn't appear to be using tagged
released, treat this as a git tree and check the updates appropriately.
Signed-off-by: Jon Mason <jon.mason@arm.com>
---
meta-arm/recipes-devtools/fvp/execstack-native.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta-arm/recipes-devtools/fvp/execstack-native.bb b/meta-arm/recipes-devtools/fvp/execstack-native.bb
index 055d39ed0646..8f22d8bab657 100644
--- a/meta-arm/recipes-devtools/fvp/execstack-native.bb
+++ b/meta-arm/recipes-devtools/fvp/execstack-native.bb
@@ -8,6 +8,10 @@ SRC_URI = "git://git.yoctoproject.org/prelink-cross;protocol=https;branch=master
SRCREV = "ff2561c02ade96c5d4d56ddd4e27ff064840a176"
PV = "1.0+git${SRCPV}"
+# The last tagged release was 20151030. Track this as a git tree to
+# see if there are any updates
+UPSTREAM_CHECK_COMMITS = "1"
+
S = "${WORKDIR}/git"
inherit autotools native
--
2.39.5 (Apple Git-154)
next prev parent reply other threads:[~2025-04-18 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 13:12 [PATCH 1/4] arm/fvps: correct broken versions Jon Mason
2025-04-18 13:12 ` [PATCH 2/4] arm/trusted-firmware-a: correct broken git version Jon Mason
2025-04-18 13:12 ` [PATCH 3/4] arm/trusted-services: correct broken git versions Jon Mason
2025-04-18 13:12 ` Jon Mason [this message]
2025-04-19 3:15 ` [PATCH 1/4] arm/fvps: correct broken versions 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=20250418131222.95241-4-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 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.