From: Lars Schmidt <l.schmidt@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Lars Schmidt <l.schmidt@pengutronix.de>
Subject: [PATCH v3 4/4] Documentation: migration-2025.08.0: add information about attempts_locked
Date: Thu, 19 Jun 2025 10:25:39 +0200 [thread overview]
Message-ID: <20250619-bootchooser-lock-v3-4-fc4ad92c3866@pengutronix.de> (raw)
In-Reply-To: <20250619-bootchooser-lock-v3-0-fc4ad92c3866@pengutronix.de>
Document the newly added feature.
Signed-off-by: Lars Schmidt <l.schmidt@pengutronix.de>
---
Documentation/migration-guides/migration-2025.08.0.rst | 5 +++++
Documentation/user/bootchooser.rst | 3 +++
2 files changed, 8 insertions(+)
diff --git a/Documentation/migration-guides/migration-2025.08.0.rst b/Documentation/migration-guides/migration-2025.08.0.rst
index d13d5c770d5e7688e0299184b0b8b938db160fca..da60132e7d8c784b08a43c8032ee7e4dc7cb7991 100644
--- a/Documentation/migration-guides/migration-2025.08.0.rst
+++ b/Documentation/migration-guides/migration-2025.08.0.rst
@@ -1,3 +1,8 @@
Release v2025.08.0
==================
+Bootchooser
+-----------
+
+Bootchooser now interprets a top-level ``attempts_locked`` variable.
+For more information, see :ref:`attempts lock feature <bootchooser,attempts_lock>`
diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst
index 1d7ece6c4b1255b41d359d3303daaf78bacfa17a..c094dca15a0e415d9076bf210ffdbece05ade62e 100644
--- a/Documentation/user/bootchooser.rst
+++ b/Documentation/user/bootchooser.rst
@@ -77,6 +77,9 @@ no remaining attempts left.
To prevent ending up in an unbootable system after a number of failed boot
attempts, there is also a built-in mechanism to reset the counters to their defaults,
controlled by the ``global.bootchooser.reset_attempts`` variable.
+
+.. _bootchooser,attempts_lock:
+
Alternatively, counting down the remaining attempts can be disabled by
locking bootchooser boot attempts.
This is done by defining a (32-bit) ``attempts_locked`` variable in the
--
2.39.5
prev parent reply other threads:[~2025-06-19 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 8:25 [PATCH v3 0/4] Add boot slot locking to bootchooser Lars Schmidt
2025-06-19 8:25 ` [PATCH v3 1/4] bootchooser: implement locking of attempts counter Lars Schmidt
2025-06-19 8:25 ` [PATCH v3 2/4] bootchooser: extend cmd tool by option to set attempts_locked Lars Schmidt
2025-06-19 8:25 ` [PATCH v3 3/4] Documentation: bootchooser: add information about attempts_locked Lars Schmidt
2025-06-19 8:25 ` Lars Schmidt [this message]
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=20250619-bootchooser-lock-v3-4-fc4ad92c3866@pengutronix.de \
--to=l.schmidt@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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