From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Tom Rini <trini@konsulko.com>
Cc: Simon Glass <sjg@chromium.org>, u-boot@lists.denx.de
Subject: Re: [PATCH 1/3] test/cmd: Make some "ut dm" tests only available on sandbox
Date: Mon, 28 Oct 2024 22:02:15 +0100 [thread overview]
Message-ID: <e29cdac5-8c91-4e6b-a7a6-e94917c12fa6@gmx.de> (raw)
In-Reply-To: <20241028164844.2308549-1-trini@konsulko.com>
On 10/28/24 17:48, Tom Rini wrote:
> Currently, the "dm" suite in unit tests (ut) is only available on
> sandbox. Make sure that all cmd tests that are part of this suite are
> only available on sandbox and not attempted to be run on hardware (where
> it will fail to be able to be started).
>
> Signed-off-by: Tom Rini <trini@konsulko.com>
Adding a comment to the sources describing that the tests require
sandbox drivers would be helpful.
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> test/cmd/Makefile | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/test/cmd/Makefile b/test/cmd/Makefile
> index 4b487c1d2cb4..fe7a2165af22 100644
> --- a/test/cmd/Makefile
> +++ b/test/cmd/Makefile
> @@ -25,16 +25,16 @@ obj-$(CONFIG_CMD_MEM_SEARCH) += mem_search.o
> ifdef CONFIG_CMD_PCI
> obj-$(CONFIG_CMD_PCI_MPS) += pci_mps.o
> endif
> -obj-$(CONFIG_CMD_PINMUX) += pinmux.o
> -obj-$(CONFIG_CMD_PWM) += pwm.o
> obj-$(CONFIG_CMD_SEAMA) += seama.o
> ifdef CONFIG_SANDBOX
> obj-$(CONFIG_CMD_MBR) += mbr.o
> +obj-$(CONFIG_CMD_PINMUX) += pinmux.o
> +obj-$(CONFIG_CMD_PWM) += pwm.o
> obj-$(CONFIG_CMD_READ) += rw.o
> obj-$(CONFIG_CMD_SETEXPR) += setexpr.o
> +obj-$(CONFIG_CMD_TEMPERATURE) += temperature.o
> ifdef CONFIG_NET
> obj-$(CONFIG_CMD_WGET) += wget.o
> endif
> obj-$(CONFIG_ARM_FFA_TRANSPORT) += armffa.o
> endif
> -obj-$(CONFIG_CMD_TEMPERATURE) += temperature.o
next prev parent reply other threads:[~2024-10-28 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 16:48 [PATCH 1/3] test/cmd: Make some "ut dm" tests only available on sandbox Tom Rini
2024-10-28 16:48 ` [PATCH 2/3] test/hush: Add CONFIG_CONSOLE_RECORD where required Tom Rini
2024-10-28 21:08 ` Heinrich Schuchardt
2024-10-28 16:48 ` [PATCH 3/3] test/lib/uuid: Make lib_test_dynamic_uuid depend on SANDBOX Tom Rini
2024-10-28 21:24 ` Heinrich Schuchardt
2024-10-28 21:34 ` Tom Rini
2024-10-28 22:01 ` Heinrich Schuchardt
2024-10-28 23:22 ` Tom Rini
2024-10-28 21:02 ` Heinrich Schuchardt [this message]
2024-10-29 22:28 ` (subset) [PATCH 1/3] test/cmd: Make some "ut dm" tests only available on sandbox Tom Rini
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=e29cdac5-8c91-4e6b-a7a6-e94917c12fa6@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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 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.