linux/meta-freescale.git/recipes-security, branch master

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

2026-08-18T20:26:37+00:00

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

optee-os-fslc: Document meta-arm SUMMARY/DESCRIPTION/HOMEPAGE for oelint

2026-08-18T20:26:37+00:00

optee-os-fslc.inc is a verbatim copy of meta-arm's optee-os.inc (see the file header and the imx-manifest reference). Its SUMMARY, DESCRIPTION and HOMEPAGE are the base OP-TEE values from that source. The optee-os-tadevkit variants re-set SUMMARY and DESCRIPTION for the devkit, so oelint.var.override reports the copied assignments as overridden. Rewriting or dropping the copied assignments would diverge from the meta-arm recipe this file mirrors and reappear on the next re-sync. Annotate the three assignments with inline "# nooelint: oelint.var.override" (UPSTREAM-PARITY) instead, matching the weston, gstreamer, libcamera and opencv i.MX forks. The suppressions bind cleanly (no inlinesuppress_na). Comment-only change; no recipe output is affected. Signed-off-by: Luciano Dittgen

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

2026-08-18T20:26:37+00:00

The previous commit stacked two "# nooelint:" comments above FILES:${PN} (one for oelint.var.filesoverride, one for oelint.var.override). Only the line immediately above the assignment bound, so oelint.var.filesoverride was left unsuppressed and fired again, and the displaced comment showed up as oelint.file.inlinesuppress_na. List both rule ids on a single "# nooelint:" line, which suppresses both as intended. Verified: oelint.var.override, oelint.var.filesoverride and oelint.file.inlinesuppress_na are all clear on the recipe. Comment-only change; no recipe output is affected. Signed-off-by: Luciano Dittgen

optee-os-qoriq-tadevkit: Document devkit FILES override for oelint

2026-08-17T21:13:24+00:00

optee-os-qoriq-tadevkit_4.8.0.bb sets FILES:${PN} = "${includedir}/optee/" because the TA devkit packages only its headers. This deliberately replaces the "${nonarch_base_libdir}/firmware/" value that the shared optee-os-fslc.inc (pulled in via optee-os.nxp.inc) sets for the base package, so oelint.var.override reports the shared value as fully replaced. The replacement is intended and cannot be expressed otherwise: - The devkit ships headers, not firmware, so the base value is wrong for it -- a genuine full replacement, not an addition, so "+=" does not apply. - optee-os-fslc.inc sets FILES:${PN} with a hard "=" to override the bitbake.conf default; weakening the shared value to "?=" would let that config default win instead, breaking the base package. Annotate the assignment with "# nooelint: oelint.var.override" (JUSTIFIED), next to the existing filesoverride note. This mirrors the optee-os-tadevkit-fslc-imx.inc devkit. Comment-only change; no recipe output is affected. Signed-off-by: Luciano Dittgen

optee-os-qoriq: Extend FILES instead of restating the shared firmware tree

2026-08-17T21:12:17+00:00

optee-os-qoriq_4.8.0.bb set FILES:${PN} = "${nonarch_base_libdir}/optee_armtz/ ${nonarch_base_libdir}/firmware/" with a hard "=", fully replacing the FILES:${PN} = "${nonarch_base_libdir}/firmware/" that the required optee-os-fslc.inc already provides. That tripped oelint.var.override, and the recipe carried a "# nooelint: oelint.var.filesoverride" note to keep the earlier filesoverride rule quiet. The qoriq main package is the shared firmware tree plus the trusted- application store -- an addition, not a different set. Express it as FILES:${PN} += "${nonarch_base_libdir}/optee_armtz/", which keeps the firmware directory from the include and appends the TA store. The resulting FILES:${PN} names the same two directories as before (FILES is an order-independent set of path globs), so packaging is unchanged. Using "+=" removes the override entirely, so both oelint.var.override and oelint.var.filesoverride now pass without any suppression; drop the stale "# nooelint: oelint.var.filesoverride" line. Validated with a real build in a resolved qoriq environment (MACHINE=ls1046ardb): FILES:${PN} resolves to the same two directories before ("optee_armtz/ firmware/") and after ("firmware/ optee_armtz/"), and comparing buildhistory across the parent and this commit shows the only delta is metadata-revs -- the packaged FILELIST and PKGSIZE are unchanged. Behaviour-preserving. Signed-off-by: Luciano Dittgen

optee-os-tadevkit-fslc-imx: Document devkit FILES override for oelint

2026-08-17T21:09:58+00:00

optee-os-tadevkit-fslc-imx.inc sets FILES:${PN} = "${includedir}/optee/" because the TA devkit packages only its headers. This deliberately replaces the "${nonarch_base_libdir}/firmware/" value that the shared optee-os-fslc.inc sets for the base package, so oelint.var.override reports the shared value as fully replaced. The replacement is intended and cannot be expressed otherwise: - The devkit ships headers, not firmware, so the base value is wrong for it -- this is a genuine full replacement, not an addition, so "+=" does not apply. - optee-os-fslc.inc sets FILES:${PN} with a hard "=" to override the bitbake.conf default; weakening the shared value to "?=" would let that config default win instead, breaking the base package. So the shared value legitimately stays "=", and the devkit legitimately replaces it. Annotate the assignment with "# nooelint: oelint.var.override" (JUSTIFIED), next to the existing filesoverride note. Comment-only change; no recipe output is affected. Signed-off-by: Luciano Dittgen

smw: Remove dead LICENSE assignment

2026-08-17T20:12:16+00:00

smw_5.3.bb assigned LICENSE twice in a row: LICENSE = "BSD-3-Clause" LICENSE = "Apache-2.0 AND BSD-3-Clause AND Zlib" The first assignment is immediately and fully overwritten by the second, so oelint.var.override reported LICENSE as set-then-replaced. The second value is the correct one: it matches LIC_FILES_CHKSUM, which covers both the smw LICENSE file and the bundled psa-arch-tests LICENSE.md. Drop the dead first assignment. The effective LICENSE is unchanged. Tested: bitbake smw for imx8mp-lpddr4-evk restored all 1668 tasks from sstate with zero reruns, and buildhistory recorded "No changes", confirming the effective license metadata is identical. Signed-off-by: Luciano Dittgen

optee-os-tadevkit-fslc-imx: Document main-package FILES override per oelint

2026-08-14T14:04:10+00:00

The recipe ships only the TA devkit headers under ${includedir}/optee and packs them explicitly, so oelint flags the FILES:${PN} as oelint.var.filesoverride. Accept it with a documented inline # nooelint. No functional change. Tested with optee-os-tadevkit on imx8mp-lpddr4-evk; buildhistory unchanged. Signed-off-by: Luciano Dittgen

optee-os-qoriq-tadevkit: Document main-package FILES override per oelint

2026-08-14T14:04:10+00:00

The recipe ships only the TA devkit headers under ${includedir}/optee and packs them explicitly, so oelint flags the FILES:${PN} as oelint.var.filesoverride. Accept it with a documented inline # nooelint. No functional change. Tested with optee-os-qoriq-tadevkit on ls1028ardb; buildhistory unchanged. Signed-off-by: Luciano Dittgen

optee-os-qoriq: Document main-package FILES override per oelint

2026-08-14T14:04:10+00:00

The recipe installs OP-TEE's trusted-application store and firmware tree and packs exactly those directories, so oelint flags the FILES:${PN} as oelint.var.filesoverride. Accept it with a documented inline # nooelint. No functional change. Tested with optee-os-qoriq on ls1028ardb; buildhistory unchanged. Signed-off-by: Luciano Dittgen