optee-os-tadevkit-fslc-imx: Combine the two oelint suppressions on one line

As with optee-os-qoriq-tadevkit, this recipe stacked two "# nooelint:"
comments above FILES:${PN}. Only the line immediately above the assignment
bound, leaving oelint.var.filesoverride unsuppressed so it fired again.

List both rule ids on a single "# nooelint:" line. Verified:
oelint.var.override, oelint.var.filesoverride and oelint.file.inlinesuppress_na
are all clear layer-wide. Comment-only change; no recipe output is affected.

Signed-off-by: Luciano Dittgen <luciano.dittgen@ossystems.com.br>

1 files changed, 5 insertions, 7 deletions

diff --git a/recipes-security/optee-imx/optee-os-tadevkit-fslc-imx.inc b/recipes-security/optee-imx/optee-os-tadevkit-fslc-imx.inc
index ab3e22994..85a679efb 100644
--- a/recipes-security/optee-imx/optee-os-tadevkit-fslc-imx.inc
+++ b/recipes-security/optee-imx/optee-os-tadevkit-fslc-imx.inc
@@ -23,13 +23,11 @@ do_deploy() {
 
 # The TA devkit ships only its headers under ${includedir}/optee, packed
 # explicitly. This deliberately replaces the "${nonarch_base_libdir}/firmware/"
-# default from optee-os-fslc.inc (the devkit has no firmware payload), so
-# oelint.var.override flags the shared value as fully replaced. The include's
-# FILES:${PN} itself overrides the bitbake.conf default with a hard "=", so a
-# "?=" here would let that config default win instead; and the devkit content
-# is not additive to the base package. Keep the full replacement. JUSTIFIED.
-# nooelint: oelint.var.filesoverride
-# nooelint: oelint.var.override
+# default from optee-os-fslc.inc (the devkit has no firmware payload). The
+# include's FILES:${PN} overrides the bitbake.conf default with a hard "=", so
+# a "?=" here would let that config default win instead; and the devkit content
+# is not additive to the base package. Keep the full replacement.
+# nooelint: oelint.var.filesoverride oelint.var.override
 FILES:${PN} = "${includedir}/optee/"
 
 # Build paths are currently embedded