From: Jiri Pirko
Date: Sat, 15 Apr 2017 10:59:03 +0200
> Sat, Apr 15, 2017 at 01:01:38AM CEST, step...@networkplumber.org wrote:
>>On Thu, 13 Apr 2017 11:30:27 +0200
>>Jiri Pirko wrote:
>>
>>> We actually took this code from teamdctl (at least it was an influence).
>>> Devlink style is so much d
Sat, Apr 15, 2017 at 01:01:38AM CEST, step...@networkplumber.org wrote:
>On Thu, 13 Apr 2017 11:30:27 +0200
>Jiri Pirko wrote:
>
>> We actually took this code from teamdctl (at least it was an influence).
>> Devlink style is so much different in every aspect from the rest of the
>> iproute2 suite.
On Thu, 13 Apr 2017 11:30:27 +0200
Jiri Pirko wrote:
> We actually took this code from teamdctl (at least it was an influence).
> Devlink style is so much different in every aspect from the rest of the
> iproute2 suite. And I did it on purpose, because it is much nicer and
> easier to read. I wou
Thu, Apr 13, 2017 at 01:45:25AM CEST, step...@networkplumber.org wrote:
>On Tue, 28 Mar 2017 17:26:54 +0200
>Jiri Pirko wrote:
>
>>
>> #define pr_err(args...) fprintf(stderr, ##args)
>> -#define pr_out(args...) fprintf(stdout, ##args)
>> +#define pr_out(args...)
On Tue, 28 Mar 2017 17:26:54 +0200
Jiri Pirko wrote:
>
> #define pr_err(args...) fprintf(stderr, ##args)
> -#define pr_out(args...) fprintf(stdout, ##args)
> +#define pr_out(args...) \
> + do {
From: Arkadi Sharshevsky
Add support for pipeline debug (dpipe). The headers are used both the
gain visibillity into the headers supported by the hardware, and to
build the headers/field database which is used by other commands.
Examples:
First we can see the headers supported by the hardware:
