Dear Simon Glass,
In message <1333179058-19598-4-git-send-email-...@chromium.org> you wrote:
> Since run_command() and run_command_list() are important and a little
> confusing, add some basic tests to check that the behaviour is correct.
>
> Note: I am not sure that this should be committed, nor
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 ?
>
>
Hi Mike,
On Sun, Apr 1, 2012 at 12:53 PM, Mike Frysinger wrote:
> On Saturday 31 March 2012 03:30:58 Simon Glass wrote:
>> --- /dev/null
>> +++ b/test/Makefile
>>
>> +include $(TOPDIR)/config.mk
>> +
>> +LIB = $(obj)libtest.o
>> +
>> +COBJS-$(CONFIG_SANDBOX) += command_ut.o
>> +
>> +COBJS
On Saturday 31 March 2012 03:30:58 Simon Glass wrote:
> --- /dev/null
> +++ b/test/Makefile
>
> +include $(TOPDIR)/config.mk
> +
> +LIB = $(obj)libtest.o
> +
> +COBJS-$(CONFIG_SANDBOX) += command_ut.o
> +
> +COBJS:= $(sort $(COBJS-y))
that sort actually needed ?
> +SRCS := $(COBJS:.o=.c)
Since run_command() and run_command_list() are important and a little
confusing, add some basic tests to check that the behaviour is correct.
Note: I am not sure that this should be committed, nor where it should go
in the source tree. Comments welcome.
To run the unit tests use the ut_cmd comman
5 matches
Mail list logo