Re: [ofa-general] Re: [PATCH v2 12/13] QLogic VNIC: Driver Kconfig and Makefile.

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Ramachandra K <ramachandra.kuchimanchi@...>
Cc: <netdev@...>, <poornima.kamath@...>, <general@...>, <amar.mudrankit@...>
Date: Monday, May 26, 2008 - 5:47 pm

> The debugging code is always compiled in and is controlled
 > at run time through vnic_debug module parameter.
 > INFINIBAND_QLGC_VNIC_DEBUG config option only controls verbose debugging
 > which adds some extra information in the debug statements (file name,
 > line number)
 > which we typically use for debug builds of the driver.  Even if this option is
 > set to 'n', users can still get all debug messages from the driver by using the
 > vnic_debug module parameter.

OK, I looked at the code.  Is there any point to having
CONFIG_INFINIBAND_QLGC_VNIC_DEBUG at all??  Is anyone going to care
about having __FILE__ and __LINE__ included in the output and want to
set this option to 'n'?

 - R.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH v2 00/13] QLogic VNIC Driver , Ramachandra K, (Mon May 19, 6:31 am)
Re: [ofa-general] Re: [PATCH v2 12/13] QLogic VNIC: Driver K..., Roland Dreier, (Mon May 26, 5:47 pm)
[PATCH v2 06/13] QLogic VNIC: IB core stack interaction, Ramachandra K, (Mon May 19, 6:34 am)