From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] commands: boot_order: note that it's OMAP specific in help text
Date: Mon, 5 Oct 2020 09:10:30 +0200 [thread overview]
Message-ID: <20201005071030.GB11648@pengutronix.de> (raw)
In-Reply-To: <20201002092955.20882-1-a.fatoum@pengutronix.de>
On Fri, Oct 02, 2020 at 11:29:55AM +0200, Ahmad Fatoum wrote:
> Kconfig and online documentation don't indicate that it's OMAP
> specific. Fix this.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> arch/arm/mach-omap/boot_order.c | 4 ++--
> commands/Kconfig | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Applied, thanks
Sascha
>
> 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_START(boot_order)
> -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")
> BAREBOX_CMD_HELP_END
>
> BAREBOX_CMD_START(boot_order)
> .cmd = cmd_boot_order,
> - BAREBOX_CMD_DESC("set warm boot order")
> + BAREBOX_CMD_DESC("set OMAP warm boot order")
> BAREBOX_CMD_OPTS("DEVICE...")
> BAREBOX_CMD_GROUP(CMD_GRP_BOOT)
> BAREBOX_CMD_HELP(cmd_boot_order_help)
> 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
> config CMD_BOOT_ORDER
> tristate
> depends on ARCH_OMAP4
> - prompt "boot_order"
> + prompt "OMAP boot_order"
> help
> - 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...
>
> --
> 2.28.0
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-10-05 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:29 Ahmad Fatoum
2020-10-05 7:10 ` Sascha Hauer [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=20201005071030.GB11648@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--subject='Re: [PATCH] commands: boot_order: note that it'\''s OMAP specific in help text' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox