public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/3] metadata: metaparse: Add bool mappings to typemap
Date: Fri, 23 Jan 2026 10:07:33 +0100	[thread overview]
Message-ID: <20260123090733.GB93219@pevik> (raw)
In-Reply-To: <20260122132059.24503-3-chrubis@suse.cz>

Hi Cyril,

> - add all boolean flags in tst_test to the typemap

> - make typemap recursive (adds child pointer to the typemap struct)

> - add typemap mappings for the need_cmds optional key

> - change the implied tags to bool

LGTM.
Reviewed-by: Petr Vorel <pvorel@suse.cz>

Later (after the release) it'd be nice to add a minimal doc (i.e. describe
structs in data_storage.h). I know that the usage is quite obvious when one has
knowledge of struct tst_test, but it's getting more complex (and will, because
if we want to get tst_net.sh support, at least getopts will need to be somehow
supported unless handled in shell).

...
>  	/* Normalize types */
> -	check_normalize_types(res);
> +	check_normalize_types(res, "",  tst_test_typemap);
very nit: 2 spaces.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-01-23  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 13:20 [LTP] [PATCH 0/3] Switch bitflags in metadata to bool Cyril Hrubis
2026-01-22 13:20 ` [LTP] [PATCH 1/3] metaparse: data_storage: Add bool type Cyril Hrubis
2026-01-23  8:33   ` Petr Vorel
2026-01-22 13:20 ` [LTP] [PATCH 2/3] metadata: metaparse: Add bool mappings to typemap Cyril Hrubis
2026-01-23  9:07   ` Petr Vorel [this message]
2026-02-11 15:40     ` Cyril Hrubis
2026-01-22 13:20 ` [LTP] [PATCH 3/3] lib: shell: Switch cmd.optional to bool Cyril Hrubis
2026-01-23  9:11   ` Petr Vorel

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=20260123090733.GB93219@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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