From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/5] test: Add a command function for test execution
Date: Mon, 4 Dec 2017 13:35:36 -0500 [thread overview]
Message-ID: <20171204183536.GJ3587@bill-the-cat> (raw)
In-Reply-To: <20171125185733.40599-2-sjg@chromium.org>
On Sat, Nov 25, 2017 at 11:57:29AM -0700, Simon Glass wrote:
> The logic to either iterate through a list of tests or pick a named test
> is common to at lest two test suits. Move this logic into a new function
> and call it from the environment tests.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171204/cef73217/attachment.sig>
next prev parent reply other threads:[~2017-12-04 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 18:57 [U-Boot] [PATCH 0/5] test: Add compression tests to pytest Simon Glass
2017-11-25 18:57 ` [U-Boot] [PATCH 1/5] test: Add a command function for test execution Simon Glass
2017-12-04 18:35 ` Tom Rini [this message]
2017-11-25 18:57 ` [U-Boot] [PATCH 2/5] test: overlay: Use cmd_ut_category() Simon Glass
2017-12-04 18:35 ` [U-Boot] [U-Boot,2/5] " Tom Rini
2017-12-04 18:35 ` Tom Rini
2017-11-25 18:57 ` [U-Boot] [PATCH 3/5] test: compression: Put test variables in a struct Simon Glass
2017-12-04 18:35 ` [U-Boot] [U-Boot, " Tom Rini
2017-11-25 18:57 ` [U-Boot] [PATCH 4/5] test/py: Allow any unit test suite to be found Simon Glass
2017-11-27 18:08 ` Stephen Warren
2017-12-04 18:35 ` [U-Boot] [U-Boot, " Tom Rini
2017-11-25 18:57 ` [U-Boot] [PATCH 5/5] test: compression: Convert to unit test framework Simon Glass
2017-12-04 18:35 ` [U-Boot] [U-Boot, " 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=20171204183536.GJ3587@bill-the-cat \
--to=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.