All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Laniel <francis.laniel@amarulasolutions.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: "Michael Nazzareno Trimarchi" <michael@amarulasolutions.com>,
	"Tom Rini" <trini@konsulko.com>, "Simon Glass" <sjg@chromium.org>,
	"Harald Seiler" <hws@denx.de>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Ramon Fried" <rfried.dev@gmail.com>,
	"Pali Rohár" <pali@kernel.org>,
	"Sean Edmond" <seanedmond@microsoft.com>,
	"Tobias Waldekranz" <tobias@waldekranz.com>,
	"Masahisa Kojima" <masahisa.kojima@linaro.org>,
	"John Keeping" <john@metanate.com>,
	"Devarsh Thakkar" <devarsht@ti.com>,
	"Nikhil M Jain" <n-jain1@ti.com>,
	"Fabrice Gasnier" <fabrice.gasnier@foss.st.com>,
	"Stefan Roese" <sr@denx.de>,
	u-boot@lists.denx.de
Subject: Re: [RFC PATCH v8 09/23] cli: Add menu for hush parser
Date: Sat, 13 May 2023 21:32:42 +0100	[thread overview]
Message-ID: <13264060.uLZWGnKmhe@pwmachine> (raw)
In-Reply-To: <e9d43b08-d862-c26a-65b7-d80734f9d3c7@gmx.de>

Le samedi 13 mai 2023, 02:03:11 WEST Heinrich Schuchardt a écrit :
> On 5/12/23 22:03, Francis Laniel wrote:
> > For the moment, the menu contains only entry: HUSH_OLD_PARSER which is the
> > default.
> > The goal is to prepare the field to add a new hush parser which guarantees
> > actual behavior is still correct.
> > 
> > Reviewed-by: Simon Glass <sjg@chromium.org>
> > Signed-off-by: Francis Laniel <francis.laniel@amarulasolutions.com>
> > ---
> > 
> >   cmd/Kconfig     | 13 +++++++++++++
> >   common/Makefile |  2 +-
> >   2 files changed, 14 insertions(+), 1 deletion(-)
> > 
> > diff --git a/cmd/Kconfig b/cmd/Kconfig
> > index 87291e2d84..2c50c9f7b5 100644
> > --- a/cmd/Kconfig
> > +++ b/cmd/Kconfig
> > @@ -23,6 +23,19 @@ config HUSH_PARSER
> > 
> >   	  If disabled, you get the old, much simpler behaviour with a 
somewhat
> >   	  smaller memory footprint.
> > 
> > +menu "Hush flavor to use"
> > +	depends on HUSH_PARSER
> > +
> > +	config HUSH_OLD_PARSER
> 
> If there will be alternative parsers in future, you should use
> choice/endchoice even if there is only one option today.

In a previous version of this contribution, I used choice.
But we then decided to use different Kconfig to permit having several parser 
living at the same time.
For the reasoning behind this, please take a look at my other mail.

> Best regards
> 
> Heinrich
> 
> > +		bool "Use hush old parser"
> > +		default y
> > +		help
> > +		  This option enables the old flavor of hush based on hush 
Busybox from
> > +		  2005.
> > +
> > +		  It is actually the default U-Boot shell when decided to use 
hush as
> > shell. +endmenu
> > +
> > 
> >   config CMDLINE_EDITING
> >   
> >   	bool "Enable command line editing"
> >   	depends on CMDLINE
> > 
> > diff --git a/common/Makefile b/common/Makefile
> > index c87bb2e78b..93d0a5a309 100644
> > --- a/common/Makefile
> > +++ b/common/Makefile
> > @@ -8,7 +8,7 @@ ifndef CONFIG_SPL_BUILD
> > 
> >   obj-y += init/
> >   obj-y += main.o
> >   obj-y += exports.o
> > 
> > -obj-$(CONFIG_HUSH_PARSER) += cli_hush.o
> > +obj-$(CONFIG_HUSH_OLD_PARSER) += cli_hush.o
> > 
> >   obj-$(CONFIG_AUTOBOOT) += autoboot.o
> >   
> >   # # boards





  reply	other threads:[~2023-05-13 20:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 20:03 [RFC PATCH v8 00/23] Modernize U-Boot shell Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 01/23] test: Add framework to test hush behavior Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 02/23] test: hush: Test hush if/else Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 03/23] test/py: hush_if_test: Remove the test file Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 04/23] test: hush: Test hush variable expansion Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 05/23] test: hush: Test hush commands list Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 06/23] test: hush: Test hush loops Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 07/23] cli: Add Busybox upstream hush.c file Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 08/23] cli: Port Busybox 2021 hush to U-Boot Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 09/23] cli: Add menu for hush parser Francis Laniel
2023-05-13  1:03   ` Heinrich Schuchardt
2023-05-13 20:32     ` Francis Laniel [this message]
2023-05-12 20:03 ` [RFC PATCH v8 10/23] global_data.h: add GD_FLG_HUSH_OLD_PARSER flag Francis Laniel
2023-05-13  1:07   ` Heinrich Schuchardt
2023-05-13 20:29     ` Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 11/23] cmd: Add new cli command Francis Laniel
2023-05-13  1:18   ` Heinrich Schuchardt
2023-05-13 20:17     ` Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 12/23] cli: Enables using hush 2021 parser as command line parser Francis Laniel
2023-05-13  1:19   ` Heinrich Schuchardt
2023-05-25  8:19     ` Patrick DELAUNAY
2023-05-12 20:03 ` [RFC PATCH v8 13/23] cli: hush_2021: Enable variables expansion for hush 2021 Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 14/23] cli: hush_2021: Add functions to be called from run_command() Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 15/23] cli: add hush 2021 as parser for run_command*() Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 16/23] test: hush: Fix instructions list tests for hush 2021 Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 17/23] test: hush: Fix variable expansion " Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 18/23] cli: hush_2021: Enable using < and > as string compare operators Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 19/23] cli: hush_2021: Enable if keyword Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 20/23] cli: hush_2021: Enable loops Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 21/23] test: hush: Fix loop tests for hush 2021 Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 22/23] cli: hush_2021: Add upstream commits up to 9th May 2023 Francis Laniel
2023-05-12 20:03 ` [RFC PATCH v8 23/23] DO NOT MERGE: only to make CI happy Francis Laniel
2023-05-12 20:44   ` Tony Dinh
2023-05-13  9:54 ` [RFC PATCH v8 00/23] Modernize U-Boot shell Peter Robinson
2023-05-13 21:42   ` Francis Laniel

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=13264060.uLZWGnKmhe@pwmachine \
    --to=francis.laniel@amarulasolutions.com \
    --cc=devarsht@ti.com \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=hws@denx.de \
    --cc=ilias.apalodimas@linaro.org \
    --cc=john@metanate.com \
    --cc=masahisa.kojima@linaro.org \
    --cc=michael@amarulasolutions.com \
    --cc=n-jain1@ti.com \
    --cc=pali@kernel.org \
    --cc=rfried.dev@gmail.com \
    --cc=seanedmond@microsoft.com \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=tobias@waldekranz.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.