> 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
| Eric Paris | [RFC 0/5] [TALPA] Intro to a linux interface for on access scanning |
| Mark Fasheh | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Linus Torvalds | Linux 2.6.21-rc4 |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
