weston: Use a recognised Upstream-Status reason for the scanner revert

Both copies of the wayland-scanner revert carried
"Inappropriate [Cross-compile Specific]", which is not one of the
recognised reasons, so oelint.file.inappropriatemsg fired on
weston_10.0.5.imx.

The revert exists because the OE build resolves wayland-scanner from the
native sysroot rather than /usr/bin, so [oe-specific] describes it and
is already used elsewhere in the layer.  Both copies are updated so they
do not drift apart.

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

2 files changed, 2 insertions, 2 deletions

diff --git a/recipes-graphics/wayland/weston-10.0.5.imx/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch b/recipes-graphics/wayland/weston-10.0.5.imx/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch
index 59f2a4b67..921b778b0 100644
--- a/recipes-graphics/wayland/weston-10.0.5.imx/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch
+++ b/recipes-graphics/wayland/weston-10.0.5.imx/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch
@@ -20,7 +20,7 @@ Thus the build fails with:
 Dropping weston 9.0.0-imx commit 7859a762 (protocol: no found
 wayland-scanner with Yocto toolchain") fixes the issue.
 
-Upstream-Status: Inappropriate [Cross-compile Specific]
+Upstream-Status: Inappropriate [oe-specific]
 Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
 ---
  protocol/meson.build | 2 +-
diff --git a/recipes-graphics/wayland/weston/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch b/recipes-graphics/wayland/weston/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch
index 4d2a333a3..25b649a8c 100644
--- a/recipes-graphics/wayland/weston/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch
+++ b/recipes-graphics/wayland/weston/0001-Revert-protocol-no-found-wayland-scanner-with-Yocto-.patch
@@ -20,7 +20,7 @@ Thus the build fails with:
 Dropping weston 9.0.0-imx commit 7859a762 (protocol: no found
 wayland-scanner with Yocto toolchain") fixes the issue.
 
-Upstream-Status: Inappropriate [Cross-compile specific]
+Upstream-Status: Inappropriate [oe-specific]
 Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
 ---
  protocol/meson.build | 2 +-