netdev - RE: [PATCH net-next v4] be2net: Fix to allow get/set of debug levels in the firmware.

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 May 2012 18:47:50 -0700
From:	<Somnath.Kotur@...lex.Com>
To:	<davem@...emloft.net>
CC:	<netdev@...r.kernel.org>, <bhutchings@...arflare.com>,
	<Suresh.Reddy@...lex.com>
Subject: RE: [PATCH net-next v4] be2net: Fix to allow get/set of debug
 levels in the firmware.

Hi David,

> 
> This doesn't apply cleanly to net-next, please respin.
>
OK, need to figure out how did that happen and will respin

> Also, you should convert your driver now to use ->msg_enable to gate all of
> your driver's kernel message logging, not just this firmware stuff.

At the moment our driver does not have any extensive logging facility, but yes
going forward we will use this infrastructure to gate all our driver's logging and will send
separate patch(es) for that in future.

Does that sound good for now?  A respin for this current patch 

Thanks
Som
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html