meta-ti: cleanup use of d.getVar()

1. drop use of True as second parameter, which is default, to align with master
2. there were instances of incorrectly passing 'd' as second parameter from
previous conversion from bb.data.getVar() usage

Signed-off-by: Denys Dmytriyenko <denys@ti.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
index 52df495d..dafaac1e 100644
--- a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
+++ b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
@@ -14,11 +14,11 @@ SRCREV = "c0afab259de59909cfe74c01f3f7fbaa147f94b5"
 
 # There's only hardfp version available
 python __anonymous() {
-    tunes = d.getVar("TUNE_FEATURES", d, 1)
+    tunes = d.getVar("TUNE_FEATURES")
     if not tunes:
         return
-    pkgn = d.getVar("PN", d, 1)
-    pkgv = d.getVar("PV", d, 1)
+    pkgn = d.getVar("PN")
+    pkgv = d.getVar("PV")
     if "callconvention-hard" not in tunes:
         bb.warn("%s-%s ONLY supports hardfp mode for now" % (pkgn, pkgv))
         raise bb.parse.SkipPackage("%s-%s ONLY supports hardfp mode for now" % (pkgn, pkgv))