From: Fathi Boudra <fathi.boudra@linaro.org>
To: meta-virtualization@lists.yoctoproject.org
Cc: Fathi Boudra <fathi.boudra@linaro.org>
Subject: [meta-virtualization][PATCH] linux-yocto: include: relax the versioned linux-yocto_*_virtualization.inc
Date: Thu, 22 Feb 2024 17:20:19 +0100 [thread overview]
Message-ID: <20240222162019.3154833-1-fathi.boudra@linaro.org> (raw)
The include content hasn't changed since February 2020 and has been only
renamed since to be tightly coupled with oe-core linux-yocto kernel
version.
It's causing unecessary breakage for layers tracking meta-virtualization
master branch layer (for CI purpose for example) and haven't updated to
latest kernel.
This commit relax the strict versioning requirement and allows the users
to have a bit more time to fix thier layers.
e.g. layers still using 6.5 kernel and haven't migrated to 6.6 are
unblocked.
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
---
..._6.6_virtualization.inc => linux-yocto_6.%_virtualization.inc} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename recipes-kernel/linux/{linux-yocto_6.6_virtualization.inc => linux-yocto_6.%_virtualization.inc} (100%)
diff --git a/recipes-kernel/linux/linux-yocto_6.6_virtualization.inc b/recipes-kernel/linux/linux-yocto_6.%_virtualization.inc
similarity index 100%
rename from recipes-kernel/linux/linux-yocto_6.6_virtualization.inc
rename to recipes-kernel/linux/linux-yocto_6.%_virtualization.inc
--
2.43.0
next reply other threads:[~2024-02-22 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 16:20 Fathi Boudra [this message]
2024-02-22 17:10 ` [meta-virtualization][PATCH] linux-yocto: include: relax the versioned linux-yocto_*_virtualization.inc Bruce Ashfield
2024-02-22 17:16 ` Fathi Boudra
2024-02-22 17:19 ` Bruce Ashfield
2024-02-22 17:37 ` Fathi Boudra
2024-02-22 17:51 ` Bruce Ashfield
2024-02-22 17:59 ` Fathi Boudra
2024-02-22 18:03 ` Bruce Ashfield
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=20240222162019.3154833-1-fathi.boudra@linaro.org \
--to=fathi.boudra@linaro.org \
--cc=meta-virtualization@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).