From: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>
To: cip-dev@lists.cip-project.org, felix.moessbauer@siemens.com,
jan.kiszka@siemens.com
Subject: [cip-dev][isar-cip-core][PATCH v3 6/6] format: classes/swupdate fix parenthesis
Date: Tue, 5 Mar 2024 17:10:59 +0100 [thread overview]
Message-ID: <20240305161128.2777211-7-Quirin.Gylstorff@siemens.com> (raw)
In-Reply-To: <20240305161128.2777211-1-Quirin.Gylstorff@siemens.com>
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
classes/swupdate.bbclass | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/classes/swupdate.bbclass b/classes/swupdate.bbclass
index 3bd0cbd..01295b0 100644
--- a/classes/swupdate.bbclass
+++ b/classes/swupdate.bbclass
@@ -63,7 +63,7 @@ IMAGE_TEMPLATE_VARS:swu = " \
# TARGET_IMAGE_UUID needs to be generated before completing the template
addtask do_transform_template after do_generate_image_uuid
-python do_extend_sw_description(){
+python do_extend_sw_description() {
cmds = d.getVar("SWU_EXTEND_SW_DESCRIPTION")
if cmds is None or not cmds.strip():
return
@@ -74,7 +74,7 @@ python do_extend_sw_description(){
do_transform_template[prefuncs] += "do_extend_sw_description"
SWU_EXTEND_SW_DESCRIPTION += "add_swu_hw_compat"
-python add_swu_hw_compat(){
+python add_swu_hw_compat() {
# create SWU_HW_COMPAT_NODE based on list of supported hw
hw_compat = d.getVar('SWU_HW_COMPAT')
if hw_compat:
@@ -86,7 +86,7 @@ python add_swu_hw_compat(){
}
SWU_EXTEND_SW_DESCRIPTION += "add_swu_compression"
-python add_swu_compression(){
+python add_swu_compression() {
# create SWU_COMPRESSION_NODE node if compression is enabled
calgo = d.getVar('SWU_COMPRESSION_TYPE')
if calgo:
@@ -110,7 +110,7 @@ def add_scripts_to_src_uri(d):
SRC_URI += "${@add_scripts_to_src_uri(d)}"
SWU_EXTEND_SW_DESCRIPTION += "add_scripts_node"
-python add_scripts_node(){
+python add_scripts_node() {
swu_scripts = d.getVar('SWU_SCRIPTS')
if not swu_scripts:
return
--
2.43.0
next prev parent reply other threads:[~2024-03-05 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 16:10 [cip-dev][isar-cip-core][PATCH v3 0/6] Make swupdate signing more robust Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 1/6] swupdate: check output of sign-swu Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 2/6] sign-swu-cms: check if key and cert are valid Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 3/6] doc: Add section about SWUpdate signing to README.swupdate.md Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 4/6] fix do not add files to each image recipe Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 5/6] format: classes/efibootguard fix spacing Quirin Gylstorff
2024-03-05 16:10 ` Quirin Gylstorff [this message]
2024-03-12 8:40 ` [cip-dev][isar-cip-core][PATCH v3 0/6] Make swupdate signing more robust Jan Kiszka
2024-03-12 18:12 ` Gylstorff Quirin
2024-03-12 18:50 ` Gylstorff Quirin
2024-03-12 19:21 ` Jan Kiszka
2024-03-13 7:57 ` Gylstorff Quirin
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=20240305161128.2777211-7-Quirin.Gylstorff@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).