From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] test: unit tests for print_freq(), print_size()
Date: Thu, 8 Oct 2020 21:23:19 -0400 [thread overview]
Message-ID: <7bb52f84-0c4e-83f4-1017-1f30d94222ce@gmail.com> (raw)
In-Reply-To: <20201008202324.51012-3-xypron.glpk@gmx.de>
On 10/8/20 4:23 PM, Heinrich Schuchardt wrote:
> Provide unit tests for functions print_freq() and print_size().
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> test/lib/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/test/lib/Makefile b/test/lib/Makefile
> index 22236f8587..15cd512506 100644
> --- a/test/lib/Makefile
> +++ b/test/lib/Makefile
> @@ -7,6 +7,7 @@ obj-$(CONFIG_EFI_LOADER) += efi_device_path.o
> obj-$(CONFIG_EFI_SECURE_BOOT) += efi_image_region.o
> obj-y += hexdump.o
> obj-y += lmb.o
> +obj-y += test_print.o
Should test/lib/test_print.c be included in this patch?
--Sean
> obj-$(CONFIG_SSCANF) += sscanf.o
> obj-y += string.o
> obj-$(CONFIG_ERRNO_STR) += test_errno_str.o
> --
> 2.28.0
>
next prev parent reply other threads:[~2020-10-09 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 20:23 [PATCH 0/2] lib: print_freq() should output kHz not KHz Heinrich Schuchardt
2020-10-08 20:23 ` [PATCH 1/2] " Heinrich Schuchardt
2020-10-09 4:12 ` Stefan Roese
2020-10-23 0:29 ` Tom Rini
2020-10-08 20:23 ` [PATCH 2/2] test: unit tests for print_freq(), print_size() Heinrich Schuchardt
2020-10-09 1:23 ` Sean Anderson [this message]
2020-10-22 13:56 ` Tom Rini
2020-10-22 19:45 [PATCH 0/2] lib: print_freq() should output kHz not KHz Heinrich Schuchardt
2020-10-22 19:45 ` [PATCH 2/2] test: unit tests for print_freq(), print_size() Heinrich Schuchardt
2020-10-24 14:52 ` 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=7bb52f84-0c4e-83f4-1017-1f30d94222ce@gmail.com \
--to=seanga2@gmail.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.