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>,
Hector Palacios <hector.palacios@digi.com>,
Marek Vasut <marex@denx.de>,
Evgeny Bachinin <EABachinin@sberdevices.ru>,
Stefan Roese <sr@denx.de>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Bin Meng <bmeng.cn@gmail.com>, Nikhil M Jain <n-jain1@ti.com>,
u-boot@lists.denx.de
Subject: Re: [RFC PATCH v8 10/23] global_data.h: add GD_FLG_HUSH_OLD_PARSER flag
Date: Sat, 13 May 2023 21:29:38 +0100 [thread overview]
Message-ID: <1852668.tdWV9SEqCh@pwmachine> (raw)
In-Reply-To: <0fa99736-6416-4086-154b-de5f2b581b6a@gmx.de>
Le samedi 13 mai 2023, 02:07:57 WEST Heinrich Schuchardt a écrit :
> On 5/12/23 22:03, Francis Laniel wrote:
> > This flag is used to indicate we are using the hush parser.
> >
> > Reviewed-by: Simon Glass <sjg@chromium.org>
> > Signed-off-by: Francis Laniel <francis.laniel@amarulasolutions.com>
> > ---
> >
> > common/cli.c | 2 ++
> > include/asm-generic/global_data.h | 4 ++++
> > 2 files changed, 6 insertions(+)
> >
> > diff --git a/common/cli.c b/common/cli.c
> > index 3916a7b10a..e5fe1060d0 100644
> > --- a/common/cli.c
> > +++ b/common/cli.c
> > @@ -268,6 +268,8 @@ void cli_loop(void)
> >
> > void cli_init(void)
> > {
> > #ifdef CONFIG_HUSH_PARSER
>
> GD_FLG_HUSH_OLD_PARSER should depend on CONFIG_HUSH_OLD_PARSER.
I am not sure how to handle this as it would mean having something like this:
#ifdef CONFIG_HUSH_OLD_PARSER
/**
* @GD_FLG_HUSH_OLD_PARSER: Use hush old parser.
*/
GD_FLG_HUSH_OLD_PARSER = 0x400000,
#endif
#ifdef CONFIG_HUSH_2021_PARSER
/**
* @GD_FLG_HUSH_2021_PARSER: Use hush 2021 parser.
*/
GD_FLG_HUSH_2021_PARSER = 0x800000,
#endif
So, this would mean some flag would exist depending on CONFIG_*, which would
then make the testing quite hard.
Indeed, for now, none of gd_flags is defined depending on some CONFIG_*.
Nonetheless, maybe using gd_flags here is not the correct solution?
Do you have in mind any idea which would be a better fit?
> Running scripts/checkpatch.pl indicates that we should use
> IS_ENABLED(CONFIG_*) here.
This code was not added in this contribution.
I may clean it but the current contribution is quite big, so I would like to
avoid making it bigger by polishing other code if possible.
I will nonetheless checkpatch.pl every commits here for the next version!
> Best regards
>
> Heinrich
>
> > + if (!(gd->flags & GD_FLG_HUSH_OLD_PARSER))
> > + gd->flags |= GD_FLG_HUSH_OLD_PARSER;
> >
> > u_boot_hush_start();
> >
> > #endif
> >
> > diff --git a/include/asm-generic/global_data.h
> > b/include/asm-generic/global_data.h index a1e1b9d640..120f1189ee 100644
> > --- a/include/asm-generic/global_data.h
> > +++ b/include/asm-generic/global_data.h
> > @@ -654,6 +654,10 @@ enum gd_flags {
> >
> > * @GD_FLG_OF_TAG_MIGRATE: Device tree has old u-boot,dm- tags
> > */
> >
> > GD_FLG_OF_TAG_MIGRATE = 0x200000,
> >
> > + /**
> > + * @GD_FLG_HUSH_OLD_PARSER: Use hush old parser.
> > + */
> > + GD_FLG_HUSH_OLD_PARSER = 0x400000,
> >
> > };
> >
> > #endif /* __ASSEMBLY__ */
next prev parent reply other threads:[~2023-05-13 20:29 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
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 [this message]
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=1852668.tdWV9SEqCh@pwmachine \
--to=francis.laniel@amarulasolutions.com \
--cc=EABachinin@sberdevices.ru \
--cc=bmeng.cn@gmail.com \
--cc=hector.palacios@digi.com \
--cc=hws@denx.de \
--cc=marex@denx.de \
--cc=michael@amarulasolutions.com \
--cc=n-jain1@ti.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox