[PATCH 2/2] arm/optee-ftpm: update recipe name

optee-ftpm tagged the 4.10 release, but had no functional changes (that
is, they tagged the same commit of 4.9.0 with 4.10.0).  Update the
recipe name to match the latest version, and not have people think that
one package was held back.

Also, modify the version checking to be less incorrect

Signed-off-by: Jon Mason <[email protected]>
---
 .../{optee-ftpm_4.9.0.bb =3D> optee-ftpm_4.10.0.bb}          | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)
 rename meta-arm/recipes-security/optee-ftpm/{optee-ftpm_4.9.0.bb =3D> op=
tee-ftpm_4.10.0.bb} (93%)

diff --git a/meta-arm/recipes-security/optee-ftpm/optee-ftpm_4.9.0.bb b/m=
eta-arm/recipes-security/optee-ftpm/optee-ftpm_4.10.0.bb
similarity index 93%
rename from meta-arm/recipes-security/optee-ftpm/optee-ftpm_4.9.0.bb
rename to meta-arm/recipes-security/optee-ftpm/optee-ftpm_4.10.0.bb
index 0cbefceeec8b..9a58f7bc0753 100644
--- a/meta-arm/recipes-security/optee-ftpm/optee-ftpm_4.9.0.bb
+++ b/meta-arm/recipes-security/optee-ftpm/optee-ftpm_4.10.0.bb
@@ -33,12 +33,15 @@ SRC_URI =3D "\
 # As per optee-ftpm TA documentation, we have to use this SHA of MS TPM =
reference
 SRCREV_ms-tpm   ?=3D "98b60a44aba79b15fcce1c0d1e46cf5918400f6a"
=20
-# v4.9.0
+# v4.10.0
 SRCREV_optee-ta ?=3D "a09269b15de635e1816fe832e26adfbfb44c5455"
=20
 SRCREV_FORMAT    =3D "ms-tpm_optee-ta"
=20
-UPSTREAM_CHECK_COMMITS =3D "1"
+# Because of the OPTEE portion being put inside of the ms-tpm, the
+# tooling usings the ms-tpm source for version and not the optee-ta.
+# So, disable checking
+UPSTREAM_VERSION_UNKNOWN =3D "1"
=20
 S =3D "${UNPACKDIR}/ms-tpm"
=20
--=20
2.50.1 (Apple Git-155)