From: Joe Perches <joe@perches.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel.h: Add a never optimized away pr_dbg for printk(KERN_DEBUG pr_fmt(fmt)...)
Date: Tue, 13 Oct 2009 21:44:12 -0700 [thread overview]
Message-ID: <1255495452.1851.13.camel@Joe-Laptop.home> (raw)
In-Reply-To: <alpine.DEB.1.00.0910132124120.2044@chino.kir.corp.google.com>
On Tue, 2009-10-13 at 21:28 -0700, David Rientjes wrote:
> The pr_dbg_* variations seem reasonable if the current pr_debug() were
> changed to pr_dbg().
I think that's unlikely to happen.
> this discussion is irrelevant if there
> are no current use cases (in which case the patch is pointless).
Yeah, right. It's alway irrelevant to add new
facilities when where are no current use cases.
I sent a 21 deep patchset over a week ago.
http://lkml.org/lkml/2009/10/4/198
prev parent reply other threads:[~2009-10-14 4:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 2:56 Joe Perches
2009-10-14 3:34 ` David Rientjes
2009-10-14 4:21 ` Joe Perches
2009-10-14 4:28 ` David Rientjes
2009-10-14 4:44 ` Joe Perches [this message]
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=1255495452.1851.13.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
/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
all inboxes | Powered by JetHome®