netdev - Re: [PATCH ] dynamic_debug: call __netdev_printk only for CONFIG

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]

Message-ID: <4E76288A.4020801@xenotime.net>
Date:	Sun, 18 Sep 2011 10:21:14 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Greg KH <greg@...ah.com>
CC:	Jason Baron <jbaron@...hat.com>, Arnd Bergmann <arnd@...db.de>,
	gregkh@...e.de, joe@...ches.com, jim.cromie@...il.com,
	bvanassche@....org, linux-kernel@...r.kernel.org,
	davem@...emloft.net, aloisio.almeida@...nbossa.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH ] dynamic_debug: call __netdev_printk only for CONFIG_NET

On 09/18/2011 01:27 AM, Greg KH wrote:
> On Thu, Sep 01, 2011 at 11:18:18AM -0400, Jason Baron wrote:
>> On Thu, Sep 01, 2011 at 04:57:02PM +0200, Arnd Bergmann wrote:
>>> __netdev_printk is only defined when CONFIG_NET is set. Since we only need
>>> __dynamic_netdev_dbg for network drivers, we can make it conditional on the
>>> same Kconfig symbol.
>>>
>>
>> Hi,
>>
>> Yes, I've posted a fix for this:
>>
>> https://lkml.org/lkml/2011/8/30/297
>>
>> Hopefully, it will be pulled in soon.
> 
> As that thread again spun off into confusion, can you please resend the
> end result?

That spinning confusion had nothing to do with the posted & correct patch
which could have been applied several weeks ago.

I'm curious:  Do you delete most of your email on a routine basis?

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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