All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>
To: felix.moessbauer@siemens.com, cip-dev@lists.cip-project.org,
	jan.kiszka@siemens.com
Subject: [cip-dev][isar-cip-core][PATCH v2 3/3] swupdate.bbclass: weak default assignment for SWU_HW_COMPAT
Date: Wed,  7 Feb 2024 14:44:27 +0100	[thread overview]
Message-ID: <20240207134505.3286003-4-Quirin.Gylstorff@siemens.com> (raw)
In-Reply-To: <20240207134505.3286003-1-Quirin.Gylstorff@siemens.com>

From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

This allows to set SWU_HW_COMPAT in recipe-core/images/swupdate.inc
and in downstream layers.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
 classes/swupdate.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/classes/swupdate.bbclass b/classes/swupdate.bbclass
index 403bdef..20589f3 100644
--- a/classes/swupdate.bbclass
+++ b/classes/swupdate.bbclass
@@ -20,7 +20,7 @@ SWU_ROOTFS_PARTITION_NAME ?= "${SWU_ROOTFS_NAME}.${SWU_ROOTFS_TYPE}${@get_swu_co
 SWU_VERSION ?= "0.2"
 SWU_NAME ?= "cip software update"
 # space separated list of supported hw. Leave empty to leave out
-SWU_HW_COMPAT ?= ""
+SWU_HW_COMPAT ??= ""
 
 SWU_EBG_UPDATE ?= ""
 SWU_EFI_BOOT_DEVICE ?= "/dev/disk/by-uuid/4321-DCBA"
-- 
2.43.0



  parent reply	other threads:[~2024-02-07 13:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 13:44 [cip-dev][isar-cip-core][PATCH v2 0/3] Reduce difference to debian Quirin Gylstorff
2024-02-07 13:44 ` [cip-dev][isar-cip-core][PATCH v2 1/3] swupdate-config: move swupdate.cfg from customizations to own recipe Quirin Gylstorff
2024-02-12 18:46   ` Jan Kiszka
2024-02-07 13:44 ` [cip-dev][isar-cip-core][PATCH v2 2/3] swupdate: set SWU_HW_COMPAT Quirin Gylstorff
2024-02-12 18:46   ` Jan Kiszka
2024-02-07 13:44 ` Quirin Gylstorff [this message]
2024-02-12 18:41 ` [cip-dev][isar-cip-core][PATCH v2 0/3] Reduce difference to debian Jan Kiszka

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=20240207134505.3286003-4-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.