mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] commands: bootchooser: migrate menu entry to boot menu
Date: Wed, 21 Oct 2020 11:52:09 +0200	[thread overview]
Message-ID: <20201021095209.GV13710@pengutronix.de> (raw)
In-Reply-To: <20201020051318.17233-1-a.fatoum@pengutronix.de>

On Tue, Oct 20, 2020 at 07:13:17AM +0200, Ahmad Fatoum wrote:
> While the bootchooser command is not required for boot with bootchooser,
> it's still boot related and is more likely to be looked for in the boot
> menu than the misc menu. The boot menu has other commands like uimage
> which do not boot either, but are boot-related.
> 
> While at it, add some Kconfig help text.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  commands/Kconfig | 22 +++++++++++++++++-----
>  1 file changed, 17 insertions(+), 5 deletions(-)

Applied, thanks

Sascha

> 
> diff --git a/commands/Kconfig b/commands/Kconfig
> index df18715f20d4..727946706300 100644
> --- a/commands/Kconfig
> +++ b/commands/Kconfig
> @@ -498,6 +498,23 @@ config CMD_UIMAGE
>  		  -e OUTFILE	extract image to OUTFILE
>  		  -n NO		use image number NO in multifile image
>  
> +config CMD_BOOTCHOOSER
> +	tristate
> +	depends on BOOTCHOOSER
> +	prompt "bootchooser control utility"
> +	help
> +	  Control misc behaviour of the bootchooser
> +
> +	  Options:
> +	    -a <n|default> [TARGETS]
> +	    	set remaining attempts of given targets to 'n' or the default attempts
> +	    -p <n|default> [TARGETS]
> +	    	set priority of given targets to 'n' or the default priority
> +	    -i
> +	    	Show information about the bootchooser
> +	    -s
> +		Mark the last boot successful
> +
>  # end Boot commands
>  endmenu
>  
> @@ -2179,11 +2196,6 @@ config CMD_STATE
>  	depends on STATE
>  	prompt "state"
>  
> -config CMD_BOOTCHOOSER
> -	tristate
> -	depends on BOOTCHOOSER
> -	prompt "bootchooser"
> -
>  config CMD_DHRYSTONE
>  	bool
>  	prompt "dhrystone"
> -- 
> 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

      parent reply	other threads:[~2020-10-21  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20  5:13 Ahmad Fatoum
2020-10-20  5:13 ` [PATCH 2/2] x86: configs: efi: enable some more useful options Ahmad Fatoum
2020-10-21  9:52 ` 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=20201021095209.GV13710@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=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