mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] fixup! defaultenv: base: add new devboot script
Date: Wed, 18 Mar 2026 16:53:41 +0100	[thread overview]
Message-ID: <20260318155341.3384253-1-a.fatoum@pengutronix.de> (raw)

defaultenv: base: devel: drop incomplete boot target

If boot.default is set to devel, what's the boot.default the boot
command uses...?

This boot target doesn't make sense and the alternative is for users to
write their own boot script, so drop the target and references to it.

Reported-by: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/user/devboot.rst          | 3 ---
 defaultenv/defaultenv-2-base/boot/devel | 3 ---
 2 files changed, 6 deletions(-)
 mode change 100755 => 100644 defaultenv/defaultenv-2-base/boot/devel

diff --git a/Documentation/user/devboot.rst b/Documentation/user/devboot.rst
index 4425f0ebe91a..550ab9120576 100644
--- a/Documentation/user/devboot.rst
+++ b/Documentation/user/devboot.rst
@@ -140,9 +140,6 @@ Usage
   # Boot from the default boot entry
   devboot
 
-  # Make devboot the default for subsequent boots
-  nv.boot.default=devel
-
 Configuration script
 ^^^^^^^^^^^^^^^^^^^^
 
diff --git a/defaultenv/defaultenv-2-base/boot/devel b/defaultenv/defaultenv-2-base/boot/devel
old mode 100755
new mode 100644
index 9bcaaffb5870..e69de29bb2d1
--- a/defaultenv/defaultenv-2-base/boot/devel
+++ b/defaultenv/defaultenv-2-base/boot/devel
@@ -1,3 +0,0 @@
-#!/bin/sh
-
-devboot
-- 
2.47.3




             reply	other threads:[~2026-03-18 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 15:53 Ahmad Fatoum [this message]
2026-03-19  6:49 ` 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=20260318155341.3384253-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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