lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 May 2008 13:07:28 +0530
From:	"Ramachandra K" <>
To:	"Roland Dreier" <>
Subject: Re: [ofa-general] Re: [PATCH v2 12/13] QLogic VNIC: Driver Kconfig and Makefile.


On Mon, May 26, 2008 at 4:13 AM, Roland Dreier <> wrote:
>  > +    bool "QLogic VNIC Verbose debugging"
>  > +    depends on INFINIBAND_QLGC_VNIC
>  > +    default n
>  > +    ---help---
>  > +      This option causes verbose debugging code to be compiled
>  > +      into the QLogic VNIC driver.  The output can be turned on via the
>  > +      vnic_debug module parameter.
> I think I mentioned this before, but... if you default this option to
> 'n', then all distributions will build your module with the option off.
> And if someone is having problems, they will be forced to rebuild their
> kernel to get debug output, which is a heavy burden for most users.

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.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists