Upgrades like 34 -> 34.1 or 34.1 -> 34.2 for kmod are stable upgrades.
* Evidence
Its repo contains a branch called:
origin/kmod-34.y
Its tags are like:
v32
v33
v34
v34.1
So we can infer that the maintenance policy for kmod is that
upgrades such as 33 -> 34 contains features and upgrades such
as 34 -> 34.1 is a stable upgrade. And such maintenance policy
is likely to continue.
[1] https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
file://libkmod/COPYING;md5=a6f89e2100d9b6cdffcea4f398e37343 \
file://tools/COPYING;md5=751419260aa954499f7abaabaa882bbe \
"
-inherit bash-completion gtk-doc manpages meson pkgconfig update-alternatives
+inherit bash-completion gtk-doc manpages meson pkgconfig update-alternatives upstream-stable-release-point
SRC_URI = "https://www.kernel.org/pub/linux/utils/kernel/${BPN}/${BP}.tar.xz \
file://depmod-search.conf \
"
SRC_URI[sha256sum] = "5a5d5073070cc7e0c7a7a3c6ec2a0e1780850c8b47b3e3892226b93ffcb9cb54"
+STABLE_VERSION_PARTS = "1"
+
EXTRA_OEMESON += "\
-Ddistconfdir=${nonarch_base_libdir} \
--bindir=${base_bindir} \