2016-05-09 17:19, Jan Viktorin:
> On Fri, 06 May 2016 16:32:53 +0200
> Thomas Monjalon wrote:
>
> > It looks a lot too much tricky to be integrated without code comments ;)
> > Please make a documentation effort.
> >
> [...]
>
> Thomas,
>
> is it OK to include the PCI test enhancements? Or
On Fri, 06 May 2016 16:32:53 +0200
Thomas Monjalon wrote:
> It looks a lot too much tricky to be integrated without code comments ;)
> Please make a documentation effort.
>
[...]
Thomas,
is it OK to include the PCI test enhancements? Or should I post only the
fixed "resource framework"?
Hello Thomas,
On Fri, 06 May 2016 16:32:53 +0200
Thomas Monjalon wrote:
> It looks a lot too much tricky to be integrated without code comments ;)
> Please make a documentation effort.
I know it's not the brightly shining code... I focused mainly on the C API of
this. Thanks a lot for
It looks a lot too much tricky to be integrated without code comments ;)
Please make a documentation effort.
2016-05-06 12:48, Jan Viktorin:
> --- a/app/test/Makefile
> +++ b/app/test/Makefile
> @@ -33,6 +33,37 @@ include $(RTE_SDK)/mk/rte.vars.mk
>
> ifeq ($(CONFIG_RTE_APP_TEST),y)
A comment
To include resources from other source that the C source code we can take
advantage of the objcopy behaviour, i.e. packing of an arbitrary file as an
object file that is linked to the target program.
A linked object file is always accessible as a pair
extern const char beg_;
extern const char
5 matches
Mail list logo