[meta-security][PATCH] linux-yocto: drop version from bbappends

[meta-security][PATCH] linux-yocto: drop version from bbappends

[Mikko Rapeli]

These bbappends apply to multiple kernel versions so no
need to make them version dependent. Fixes recipe parsing when
using meta-security master branch on kirkstone. In our custom layer we
set layer compatibility for kirkstone and I understand why meta-security
upstream would not want to do that:

LAYERSERIES_COMPAT_security-layer += 'kirkstone'
LAYERSERIES_COMPAT_parsec-layer += 'kirkstone'
LAYERSERIES_COMPAT_tpm-layer += 'kirkstone'

While I work towards supporting also yocto master branch and newer
releases than kirkstone, I would appreciate if I would not have to
branch off layers over minor details like this.

Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
---
 .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}    | 0
 .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}    | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename meta-tpm/recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)
 rename recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)

diff --git a/meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend b/meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend
similarity index 100%
rename from meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend
rename to meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend
diff --git a/recipes-kernel/linux/linux-yocto_6.%.bbappend b/recipes-kernel/linux/linux-yocto_%.bbappend
similarity index 100%
rename from recipes-kernel/linux/linux-yocto_6.%.bbappend
rename to recipes-kernel/linux/linux-yocto_%.bbappend
-- 
2.34.1

[meta-security][PATCH] linux-yocto: drop version from bbappends

[Mikko Rapeli]

These bbappends apply to multiple kernel versions so no
need to make them version dependent. Fixes recipe parsing when
using meta-security master branch on kirkstone. In our custom layer we
set layer compatibility for kirkstone and I understand why meta-security
upstream would not want to do that:

LAYERSERIES_COMPAT_security-layer += 'kirkstone'
LAYERSERIES_COMPAT_parsec-layer += 'kirkstone'
LAYERSERIES_COMPAT_tpm-layer += 'kirkstone'

While I work towards supporting also yocto master branch and newer
releases than kirkstone, I would appreciate if I would not have to
branch off layers over minor details like this.

Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
---
 .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}    | 0
 .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}    | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename meta-tpm/recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)
 rename recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)

diff --git a/meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend b/meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend
similarity index 100%
rename from meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend
rename to meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend
diff --git a/recipes-kernel/linux/linux-yocto_6.%.bbappend b/recipes-kernel/linux/linux-yocto_%.bbappend
similarity index 100%
rename from recipes-kernel/linux/linux-yocto_6.%.bbappend
rename to recipes-kernel/linux/linux-yocto_%.bbappend
-- 
2.34.1