From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 26 May 2026 21:37:59 +0200 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wRxbD-0048kt-2b for lore@lore.pengutronix.de; Tue, 26 May 2026 21:37:59 +0200 Received: from [127.0.0.1] (helo=metis.whiteo.stw.pengutronix.de) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1wRxbD-00039F-Ck; Tue, 26 May 2026 21:37:59 +0200 Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1wRxb4-0002nb-07; Tue, 26 May 2026 21:37:50 +0200 Received: from dude05.red.stw.pengutronix.de ([2a0a:edc0:0:1101:1d::54]) by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wRxb3-001zPg-0v; Tue, 26 May 2026 21:37:49 +0200 Received: from [::1] (helo=dude05.red.stw.pengutronix.de) by dude05.red.stw.pengutronix.de with esmtp (Exim 4.98.2) (envelope-from ) id 1wRxb3-00000001DHA-3BYa; Tue, 26 May 2026 21:37:49 +0200 From: Ahmad Fatoum To: distrokit@pengutronix.de Date: Tue, 26 May 2026 21:36:43 +0200 Message-ID: <20260526193736.288664-3-a.fatoum@pengutronix.de> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260526193736.288664-1-a.fatoum@pengutronix.de> References: <20260526193736.288664-1-a.fatoum@pengutronix.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [DistroKit] [PATCH 2/9] v7a: vexpress: do not save environment on missing-bootsource X-BeenThere: distrokit@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: DistroKit Mailinglist List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Ahmad Fatoum Sender: "DistroKit" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: distrokit-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false saveenv persists the newly added scripts to flash, but the scripts are generated anew on each boot anyway. It's thus perfectly fine to just leave them in memory and save the time needed to write them out as well as the associated message, which can be confusing to users: saving environment to /dev/nor0.barebox-environment Signed-off-by: Ahmad Fatoum --- configs/platform-v7a/barebox-defaultenv/init/missing-bootsource | 1 - 1 file changed, 1 deletion(-) diff --git a/configs/platform-v7a/barebox-defaultenv/init/missing-bootsource b/configs/platform-v7a/barebox-defaultenv/init/missing-bootsource index d8637c540803..4161b4590ea1 100644 --- a/configs/platform-v7a/barebox-defaultenv/init/missing-bootsource +++ b/configs/platform-v7a/barebox-defaultenv/init/missing-bootsource @@ -15,4 +15,3 @@ for part in root-A root-B; do echo -a /env/boot/bootsource.${part} "boot ${realbootsource}.${part}" fi done -saveenv -- 2.47.3