>> >Either other "debug" logs can be put as INFO level, or
>> >you need a level 9 for verbose debug.
>> >But I don't really understand what is the problem of a verbose debug.
>> >
>> >It is not critical for the acceptance of this patch. Just wanted to
>> >discuss
>> >it as we have many config opti
> >Either other "debug" logs can be put as INFO level, or
> >you need a level 9 for verbose debug.
> >But I don't really understand what is the problem of a verbose debug.
> >
> >It is not critical for the acceptance of this patch. Just wanted to
> >discuss
> >it as we have many config options to t
>2015-10-23 22:28, Harish Patil:
>> >2015-09-11 17:42, Rasesh Mody:
>> >> From: Harish Patil
>> >> --- a/config/common_linuxapp
>> >> +++ b/config/common_linuxapp
>> >> @@ -220,6 +220,7 @@ CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=n
>> >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=n
>> >> CONFIG_RTE_LIBRTE_BNX2
2015-10-23 22:28, Harish Patil:
> >2015-09-11 17:42, Rasesh Mody:
> >> From: Harish Patil
> >> --- a/config/common_linuxapp
> >> +++ b/config/common_linuxapp
> >> @@ -220,6 +220,7 @@ CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=n
> >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=n
> >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_T
>
>2015-09-11 17:42, Rasesh Mody:
>> From: Harish Patil
>> --- a/config/common_linuxapp
>> +++ b/config/common_linuxapp
>> @@ -220,6 +220,7 @@ CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=n
>> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=n
>> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=n
>> CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=n
2015-09-11 17:42, Rasesh Mody:
> From: Harish Patil
> --- a/config/common_linuxapp
> +++ b/config/common_linuxapp
> @@ -220,6 +220,7 @@ CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=n
> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=n
> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=n
> CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=n
> +CONFIG
From: Harish Patil
Signed-off-by: Harish Patil
---
config/common_linuxapp |1 +
drivers/net/bnx2x/Makefile |2 +-
drivers/net/bnx2x/bnx2x.h |2 +-
drivers/net/bnx2x/bnx2x_logs.h |8
drivers/net/bnx2x/debug.c | 24 ++--
5 files
7 matches
Mail list logo