From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 4/4] sandbox: Add basic test for command execution
Date: Sun, 8 Apr 2012 04:40:21 -0400 [thread overview]
Message-ID: <201204080440.23935.vapier@gentoo.org> (raw)
In-Reply-To: <CAPnjgZ14xSeKwDz-kh2L0Mny9AuGp_D3yfzTPRUQ=f9XDkNz7g@mail.gmail.com>
On Wednesday 04 April 2012 03:18:30 Simon Glass wrote:
> On Sun, Apr 1, 2012 at 12:53 PM, Mike Frysinger wrote:
> > On Saturday 31 March 2012 03:30:58 Simon Glass wrote:
> >> +static int do_ut_cmd(cmd_tbl_t *cmdtp, int flag, int argc, char * const
> >
> > what is "ut" supposed to stand for ?
>
> Unit test, as normally needed by code that is utterly tortuous.
i'd use "unit test" in the cmd help string then
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120408/4d1efa41/attachment.pgp>
next prev parent reply other threads:[~2012-04-08 8:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 7:30 [U-Boot] [PATCH v3 1/4] Add run_command_list() to run a list of commands Simon Glass
2012-03-31 7:30 ` [U-Boot] [PATCH v3 2/4] Allow newlines within command environment vars Simon Glass
2012-08-09 20:06 ` Wolfgang Denk
2012-03-31 7:30 ` [U-Boot] [PATCH v3 3/4] sandbox: Use the new run_command() Simon Glass
2012-04-01 19:53 ` Mike Frysinger
2012-04-23 20:54 ` Wolfgang Denk
2012-03-31 7:30 ` [U-Boot] [PATCH v3 4/4] sandbox: Add basic test for command execution Simon Glass
2012-04-01 19:53 ` Mike Frysinger
2012-04-04 7:18 ` Simon Glass
2012-04-08 8:40 ` Mike Frysinger [this message]
2012-08-09 20:06 ` Wolfgang Denk
2012-04-01 19:48 ` [U-Boot] [PATCH v3 1/4] Add run_command_list() to run a list of commands Mike Frysinger
2012-04-04 7:12 ` Simon Glass
2012-04-08 8:39 ` Mike Frysinger
2012-04-09 4:46 ` Simon Glass
2012-08-09 20:06 ` Wolfgang Denk
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=201204080440.23935.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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