From: Randy Dunlap <rdunlap@xenotime.net>
To: Greg KH <greg@kroah.com>
Cc: Jason Baron <jbaron@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
gregkh@suse.de, joe@perches.com, jim.cromie@gmail.com,
bvanassche@acm.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, aloisio.almeida@openbossa.org,
netdev@vger.kernel.org
Subject: Re: [PATCH ] dynamic_debug: call __netdev_printk only for CONFIG_NET
Date: Sun, 18 Sep 2011 11:42:12 -0700 [thread overview]
Message-ID: <4E763B84.80009@xenotime.net> (raw)
In-Reply-To: <20110918182714.GA32615@kroah.com>
On 09/18/2011 11:27 AM, Greg KH wrote:
> On Sun, Sep 18, 2011 at 10:21:14AM -0700, Randy Dunlap wrote:
>> 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?
>
> No, only after going through pending patches do I purge them. And when
> a series of patches generates a thread like this one, where people are
> arguing over the way the macros are named, and no one seems to agree, I
> will take it as the fact that this series was contentious and needs to
> be resent after taking into consideration the original complaints.
Sheesh. The naming of the macros has nothing to do with this build fix.
> For me to keep all email threads, based on the amount of email I get[1],
> would be ludicrous.
>
> greg k-h
>
> [1]: http://www.kroah.com/log/linux/get_lots_of_email.html
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-09-18 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 18:36 [PATCH 00/11] various fixes v3 Jason Baron
2011-08-11 18:36 ` [PATCH 01/11] dynamic_debug: Add __dynamic_dev_dbg Jason Baron
2011-08-11 18:36 ` [PATCH 07/11] dynamic_debug: make netdev_dbg() call __netdev_printk() Jason Baron
2011-09-01 14:57 ` [PATCH ] dynamic_debug: call __netdev_printk only for CONFIG_NET Arnd Bergmann
2011-09-01 15:18 ` Jason Baron
2011-09-18 8:27 ` Greg KH
2011-09-18 17:21 ` Randy Dunlap
2011-09-18 18:27 ` Greg KH
2011-09-18 18:42 ` Randy Dunlap [this message]
2011-09-19 13:48 ` Jason Baron
2011-09-19 16:49 ` Randy Dunlap
2011-08-11 18:36 ` [PATCH 08/11] dynamic_debug: make netif_dbg() call __netdev_printk() Jason Baron
2011-08-23 1:32 ` [PATCH 00/11] various fixes v3 Greg KH
2011-08-23 13:54 ` Jason Baron
2011-08-23 15:15 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E763B84.80009@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=aloisio.almeida@openbossa.org \
--cc=arnd@arndb.de \
--cc=bvanassche@acm.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jbaron@redhat.com \
--cc=jim.cromie@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).