mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <>
Cc: Ahmad Fatoum <>
Subject: [PATCH] commands: boot_order: note that it's OMAP specific in help text
Date: Fri,  2 Oct 2020 11:29:55 +0200	[thread overview]
Message-ID: <> (raw)

Kconfig and online documentation don't indicate that it's OMAP
specific. Fix this.

Signed-off-by: Ahmad Fatoum <>
 arch/arm/mach-omap/boot_order.c | 4 ++--
 commands/Kconfig                | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/arch/arm/mach-omap/boot_order.c b/arch/arm/mach-omap/boot_order.c
index db22513bde42..4b74fdba66b6 100644
--- a/arch/arm/mach-omap/boot_order.c
+++ b/arch/arm/mach-omap/boot_order.c
@@ -70,13 +70,13 @@ static int cmd_boot_order(int argc, char *argv[])
-BAREBOX_CMD_HELP_TEXT("Set warm boot order of up to four devices. Each device can be one of:")
+BAREBOX_CMD_HELP_TEXT("Set OMAP warm boot order of up to four devices. Each device can be one of:")
 BAREBOX_CMD_HELP_TEXT("xip xipwait nand onenand mmc1 mmc2_1 mmc2_2 uart usb_1 usb_ulpi usb_2")
 	.cmd		= cmd_boot_order,
-	BAREBOX_CMD_DESC("set warm boot order")
+	BAREBOX_CMD_DESC("set OMAP warm boot order")
diff --git a/commands/Kconfig b/commands/Kconfig
index 9114d3cb31a5..df18715f20d4 100644
--- a/commands/Kconfig
+++ b/commands/Kconfig
@@ -285,9 +285,9 @@ config CMD_AT91_BOOT_TEST
 	depends on ARCH_OMAP4
-	prompt "boot_order"
+	prompt "OMAP boot_order"
-	  Set warm boot order (the next boot device on a warm reset).
+	  Set OMAP warm boot order (the next boot device on a warm reset).
 	  Usage: boot_order DEVICE...

barebox mailing list

             reply	other threads:[~2020-10-02  9:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  9:29 Ahmad Fatoum [this message]
2020-10-05  7:10 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: [PATCH] commands: boot_order: note that it'\''s OMAP specific in help text' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox