[dpdk-dev] [PATCH] mk: fix verbosity zero

2016-09-23 Thread Thomas Monjalon
2016-09-23 10:33, Ferruh Yigit: > On 9/23/2016 12:42 AM, Thomas Monjalon wrote: > > Verbosity is considered enabled when $V is not empty. > > So V=0 and V=1 are equivalent. > > It is fixed by unsetting V when it is 0. > > > > A side effect is to fix kernel module compilation verbosity > > which is

[dpdk-dev] [PATCH] mk: fix verbosity zero

2016-09-23 Thread Thomas Monjalon
2016-09-23 10:06, Ferruh Yigit: > On 9/23/2016 12:42 AM, Thomas Monjalon wrote: > > Verbosity is considered enabled when $V is not empty. > > So V=0 and V=1 are equivalent. > > It is fixed by unsetting V when it is 0. > > > > A side effect is to fix kernel module compilation verbosity > > which is

[dpdk-dev] [PATCH] mk: fix verbosity zero

2016-09-23 Thread Ferruh Yigit
On 9/23/2016 12:42 AM, Thomas Monjalon wrote: > Verbosity is considered enabled when $V is not empty. > So V=0 and V=1 are equivalent. > It is fixed by unsetting V when it is 0. > > A side effect is to fix kernel module compilation verbosity > which is set to 0 when V is empty. > > Reported-by: F

[dpdk-dev] [PATCH] mk: fix verbosity zero

2016-09-23 Thread Ferruh Yigit
On 9/23/2016 12:42 AM, Thomas Monjalon wrote: > Verbosity is considered enabled when $V is not empty. > So V=0 and V=1 are equivalent. > It is fixed by unsetting V when it is 0. > > A side effect is to fix kernel module compilation verbosity > which is set to 0 when V is empty. > > Reported-by: F

[dpdk-dev] [PATCH] mk: fix verbosity zero

2016-09-23 Thread Thomas Monjalon
Verbosity is considered enabled when $V is not empty. So V=0 and V=1 are equivalent. It is fixed by unsetting V when it is 0. A side effect is to fix kernel module compilation verbosity which is set to 0 when V is empty. Reported-by: Ferruh Yigit Signed-off-by: Thomas Monjalon --- mk/rte.sdkro