public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Frank Wunderlich <linux@fw-web.de>
Cc: Frank Wunderlich <frank-w@public-files.de>,
	u-boot@lists.denx.de, Daniel Golle <daniel@makrotopia.org>
Subject: Re: [PATCH v6 2/3] test: cmd: add test for memsize
Date: Tue, 3 Feb 2026 17:34:02 -0600	[thread overview]
Message-ID: <20260203233402.GU2603314@bill-the-cat> (raw)
In-Reply-To: <20260125131254.23210-3-linux@fw-web.de>

[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]

On Sun, Jan 25, 2026 at 02:12:52PM +0100, Frank Wunderlich wrote:

> From: Frank Wunderlich <frank-w@public-files.de>
> 
> Add a test for memsize command in same way as meminfo.
> 
> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> ---
> tested via:
> $ ./u-boot -T -c "ut cmd cmd_test_memsize"
> ...
> Test: memsize: meminfo.c
> Tests run: 1, 0 ms, average: 0 ms, failures: 0
> ---
>  cmd/Kconfig        |  1 +
>  test/cmd/meminfo.c | 17 +++++++++++++++++
>  2 files changed, 18 insertions(+)
> 
> diff --git a/cmd/Kconfig b/cmd/Kconfig
> index be79bf0747df..2bafa156ca8a 100644
> --- a/cmd/Kconfig
> +++ b/cmd/Kconfig
> @@ -927,6 +927,7 @@ config CMD_MEMINFO_MAP
>  
>  config CMD_MEMSIZE
>  	bool "memsize"
> +	default y if SANDBOX
>  	depends on CMD_MEMINFO
>  	help
>  	  Get RAM via command for use in scripts.
> diff --git a/test/cmd/meminfo.c b/test/cmd/meminfo.c
> index 53b41e3b49e0..ba772a8b7616 100644
> --- a/test/cmd/meminfo.c
> +++ b/test/cmd/meminfo.c
> @@ -7,6 +7,7 @@
>   */
>  
>  #include <dm/test.h>
> +#include <env.h>
>  #include <test/cmd.h>
>  #include <test/ut.h>
>  
> @@ -39,4 +40,20 @@ static int cmd_test_meminfo(struct unit_test_state *uts)
>  
>  	return 0;
>  }
> +
> +/* Test 'memsize' command */
> +static int cmd_test_memsize(struct unit_test_state *uts)
> +{
> +	ut_assertok(run_command("memsize", 0));
> +	ut_assert_nextline("256 MiB");
> +	ut_assert_console_end();
> +
> +	ut_assertok(run_command("memsize memsz", 0));
> +	ut_asserteq_str("256", env_get("memsz"));
> +	ut_assert_console_end();
> +
> +	return 0;
> +}
> +
>  CMD_TEST(cmd_test_meminfo, UTF_CONSOLE);
> +CMD_TEST(cmd_test_memsize, UTF_CONSOLE);

Since the new test isn't guarded with memsize, this fails on qemu-x86_64
where meminfo is enabled, but memsize is not.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-02-03 23:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-25 13:12 [PATCH v6 0/3] Add command for getting ramsize in scripts Frank Wunderlich
2026-01-25 13:12 ` [PATCH v6 1/3] cmd: mem: add command for getting ram size for use " Frank Wunderlich
2026-01-25 13:12 ` [PATCH v6 2/3] test: cmd: add test for memsize Frank Wunderlich
2026-02-03 23:34   ` Tom Rini [this message]
2026-02-04  6:40     ` Frank Wunderlich
2026-02-04 13:53       ` Tom Rini
2026-02-04 14:48         ` Frank Wunderlich
2026-02-04 14:51           ` Tom Rini
2026-01-25 13:12 ` [PATCH v6 3/3] doc: cmd: add usage doc " Frank Wunderlich

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=20260203233402.GU2603314@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=daniel@makrotopia.org \
    --cc=frank-w@public-files.de \
    --cc=linux@fw-web.de \
    --cc=u-boot@lists.denx.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