From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com, Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v1 06/11] meta: remove non recommended syntax
Date: Tue, 21 Jun 2022 16:38:51 +0300 [thread overview]
Message-ID: <20220621133856.4673-7-amikan@ilbers.de> (raw)
In-Reply-To: <20220621133856.4673-1-amikan@ilbers.de>
"X_append .=" is not a recommended operator combination in the latest
Bitbake versions. There is no need in using append here, so remove it.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta/recipes-kernel/kselftest/kselftest.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/kselftest/kselftest.inc b/meta/recipes-kernel/kselftest/kselftest.inc
index 6187d8e..3a0b055 100644
--- a/meta/recipes-kernel/kselftest/kselftest.inc
+++ b/meta/recipes-kernel/kselftest/kselftest.inc
@@ -44,8 +44,8 @@ KSELFTEST_SKIP_TARGETS ?= ""
KSELFTEST_FORCE_TARGETS ?= "0"
KSELFTEST_ARGS = "${@ "TARGETS=\"${KSELFTEST_TARGETS}\"" if d.getVar('KSELFTEST_TARGETS', True) else ''}"
-KSELFTEST_ARGS_append = "${@ " FORCE_TARGETS=1" if d.getVar('KSELFTEST_FORCE_TARGETS', True) == '1' else ''}"
-KSELFTEST_ARGS_append .= "${@ " SKIP_TARGETS=\"${KSELFTEST_SKIP_TARGETS}\"" if d.getVar('KSELFTEST_SKIP_TARGETS', True) else ''}"
+KSELFTEST_ARGS .= "${@ " FORCE_TARGETS=1" if d.getVar('KSELFTEST_FORCE_TARGETS', True) == '1' else ''}"
+KSELFTEST_ARGS .= "${@ " SKIP_TARGETS=\"${KSELFTEST_SKIP_TARGETS}\"" if d.getVar('KSELFTEST_SKIP_TARGETS', True) else ''}"
do_prepare_build[cleandirs] += "${S}/debian"
do_prepare_build() {
--
2.17.1
next prev parent reply other threads:[~2022-06-21 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:38 [PATCH v1 00/11] Migrate to Bitbake 2.0 Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 01/11] meta: change deprecated parse calls Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 02/11] scripts/contrib: Add override conversion script Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 03/11] scripts/contrib: configure " Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 04/11] dpkg-base: fix conflicting variable names Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 05/11] meta-isar: set default branch names Anton Mikanovich
2022-06-21 13:38 ` Anton Mikanovich [this message]
2022-06-21 13:38 ` [PATCH v1 07/11] bitbake: Update to Bitbake 2.0.1 Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 08/11] doc: require zstd tool Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 09/11] meta: update bitbake variables Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 10/11] meta: mark network access required tasks Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 11/11] meta: update overrides syntax Anton Mikanovich
2022-06-21 14:49 ` [PATCH v1 00/11] Migrate to Bitbake 2.0 Schmidt, Adriaan
2022-06-21 15:07 ` Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220621133856.4673-7-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox