From: Qi.Chen@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: alex.kanavin@gmail.com, randy.macleod@windriver.com
Subject: [OE-core][PATCH V5 6/7] util-linux: inherit upstream-stable-release-point
Date: Wed, 13 May 2026 13:23:33 +0800 [thread overview]
Message-ID: <20260513052334.2271800-6-Qi.Chen@windriver.com> (raw)
In-Reply-To: <20260513052334.2271800-1-Qi.Chen@windriver.com>
From: Chen Qi <Qi.Chen@windriver.com>
util-linux has x.y.z version scheme and the bump in z is a stable
version upgrade. For example, 2.41.1 -> 2.41.2 is a stable version
upgrade.
* Evidence
Its repo[1] contains branches like:
origin/stable/v2.39
origin/stable/v2.40
origin/stable/v2.41
[1] https://github.com/util-linux/util-linux.git
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
meta/recipes-core/util-linux/util-linux.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
index 0235862666..1068e24b76 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -25,4 +25,6 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
SRC_URI[sha256sum] = "3330d873f0fceb5560b89a7dc14e4f3288bbd880e96903ed9b50ec2b5799e58b"
+inherit upstream-stable-release-point
+
CVE_PRODUCT = "util-linux"
--
2.34.1
next prev parent reply other threads:[~2026-05-13 5:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 5:23 [OE-core][PATCH V5 1/7] recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 2/7] upstream-stable-release-point.bbclass: add bbclass for stable point upgrade Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 3/7] vte: inherit upstream-stable-release-point Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 4/7] systemd: " Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 5/7] kmod: " Qi.Chen
2026-05-13 5:23 ` Qi.Chen [this message]
2026-05-13 5:23 ` [OE-core][PATCH V5 7/7] openssh: set UPSTREAM_STABLE_RELEASE_REGEX Qi.Chen
2026-05-13 9:35 ` [OE-core][PATCH V5 1/7] recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status Alexander Kanavin
2026-05-13 9:44 ` Daniel Turull
2026-05-13 9:51 ` Alexander Kanavin
2026-05-14 4:27 ` Chen, Qi
2026-05-14 4:16 ` Chen, Qi
2026-05-14 10:38 ` Mathieu Dubois-Briand
2026-05-15 9:06 ` Chen, Qi
2026-05-15 10:22 ` Alexander Kanavin
2026-05-15 11:00 ` Mathieu Dubois-Briand
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=20260513052334.2271800-6-Qi.Chen@windriver.com \
--to=qi.chen@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.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.