From: Bastian Krause <bst@pengutronix.de>
To: barebox@lists.infradead.org
Cc: "Enrico Jörns" <ejo@pengutronix.de>,
"Bastian Krause" <bst@pengutronix.de>
Subject: [PATCH 2/9] doc: bootchooser: drop confusing description for "remaining_attempts"
Date: Mon, 31 Mar 2025 14:49:25 +0200 [thread overview]
Message-ID: <20250331124932.901033-2-bst@pengutronix.de> (raw)
In-Reply-To: <20250331124932.901033-1-bst@pengutronix.de>
"Every attempt counter reaches zero" is not how redundant booting is
meant to be used. Usually userspace or the next barebox boot increments
the counter again. This sentence is at least confusing, so drop it
altogether.
Signed-off-by: Bastian Krause <bst@pengutronix.de>
---
Documentation/user/bootchooser.rst | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst
index e318b245c14..fc36f8fb1ca 100644
--- a/Documentation/user/bootchooser.rst
+++ b/Documentation/user/bootchooser.rst
@@ -70,9 +70,7 @@ means the boot target is disabled.
When booting, *bootchooser* starts the boot target with the highest ``priority`` that
has a non-zero ``remaining_attempts`` counter. With every start of a boot target the
-``remaining_attempts`` counter of this boot target is decremented by one. This means
-every boot target's ``remaining_attempts`` counter reaches zero sooner or later and
-the boot target won't be booted anymore.
+``remaining_attempts`` counter of this boot target is decremented by one.
This behavior assures that one can retry booting a target a limited number of
times to handle temporary issues (such as power outage) and optionally allows
booting a fallback in case of a permanent failure.
--
2.39.5
next prev parent reply other threads:[~2025-03-31 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 12:49 [PATCH 1/9] doc: bootchooser: drop article before bootchooser Bastian Krause
2025-03-31 12:49 ` Bastian Krause [this message]
2025-03-31 12:49 ` [PATCH 3/9] doc: bootchooser: clarify marking boot successful from barebox Bastian Krause
2025-03-31 12:49 ` [PATCH 4/9] doc: bootchooser: don't recommend NV backend Bastian Krause
2025-03-31 12:49 ` [PATCH 5/9] doc: bootchooser: move global.bootchooser.reset_attempts docs down to other variables Bastian Krause
2025-03-31 12:49 ` [PATCH 6/9] doc: bootchooser: rephrase global.bootchooser.reset_priorities description Bastian Krause
2025-03-31 12:49 ` [PATCH 7/9] doc: bootchooser: document defaults of global.bootchooser.* Bastian Krause
2025-03-31 12:49 ` [PATCH 8/9] doc: bootchooser: rephrase scenarios Bastian Krause
2025-03-31 12:49 ` [PATCH 9/9] doc: bootchooser: document NV storage backend separately Bastian Krause
2025-04-01 6:06 ` [PATCH 1/9] doc: bootchooser: drop article before bootchooser Sascha Hauer
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=20250331124932.901033-2-bst@pengutronix.de \
--to=bst@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ejo@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