DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [DistroKit] [PATCH 2/9] v7a: vexpress: do not save environment on missing-bootsource
Date: Tue, 26 May 2026 21:36:43 +0200	[thread overview]
Message-ID: <20260526193736.288664-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20260526193736.288664-1-a.fatoum@pengutronix.de>

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 <a.fatoum@pengutronix.de>
---
 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




  parent reply	other threads:[~2026-05-26 19:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 19:36 [DistroKit] [PATCH 0/9] v7a: vexpress: Switch from vexpress-a9 to virt Ahmad Fatoum
2026-05-26 19:36 ` [DistroKit] [PATCH 1/9] v7a: rauc: fix /dev/disk/by-usage symlinks for FairyTux 2 Ahmad Fatoum
2026-05-26 19:36 ` Ahmad Fatoum [this message]
2026-05-26 19:36 ` [DistroKit] [PATCH 3/9] datapartition: fix regex for virtualized block devices Ahmad Fatoum
2026-05-26 19:36 ` [DistroKit] [PATCH 4/9] v7a: delete non-functional run-nfs Ahmad Fatoum
2026-05-26 19:36 ` [DistroKit] [PATCH 5/9] v7a: run: drop non-functional scsi option Ahmad Fatoum
2026-05-26 19:36 ` [DistroKit] [PATCH 6/9] v7a: vexpress: drop non-functional 9p boot target Ahmad Fatoum
2026-05-26 19:36 ` [DistroKit] [PATCH 7/9] v7a: vexpress: Switch from vexpress-a9 to virt Ahmad Fatoum
2026-05-26 19:36 ` [DistroKit] [PATCH 8/9] v7a: run: do not shutdown on reboot Ahmad Fatoum
2026-05-26 19:36 ` [DistroKit] [PATCH 9/9] Revert "platform-v7a: vexpress: use only one core for barebox" Ahmad Fatoum

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=20260526193736.288664-3-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    /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