From: Joe Perches <joe@perches.com>
To: Jason Baron <jbaron@redhat.com>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] dynamic_debug
Date: Thu, 30 Jun 2011 11:14:33 -0700 [thread overview]
Message-ID: <cover.1309457340.git.joe@perches.com> (raw)
In-Reply-To: <20110630163218.GA2457@redhat.com>
Some improvements and cleanups to dynamic_debug
btw Jason:
You're not listed in MAINTAINERS for dynamic_debug.[ch].
Maybe you should add yourself.
Joe Perches (4):
dynamic_debug: Add __dynamic_dev_dbg
dynamic_debug: Consolidate prefix output to single routine
dynamic_debug: Remove uses of KERN_CONT in dynamic_emit_prefix
dynamic_debug: Convert printks to pr_<level>
drivers/base/core.c | 5 +-
include/linux/device.h | 5 ++
include/linux/dynamic_debug.h | 10 +++-
lib/dynamic_debug.c | 133 +++++++++++++++++++++++++++--------------
4 files changed, 103 insertions(+), 50 deletions(-)
--
1.7.6.rc1
next parent reply other threads:[~2011-06-30 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110630163218.GA2457@redhat.com>
2011-06-30 18:14 ` Joe Perches [this message]
2011-06-30 18:14 ` [PATCH 1/4] dynamic_debug: Add __dynamic_dev_dbg Joe Perches
2011-06-30 19:51 ` [PATCH 0/4] dynamic_debug Jason Baron
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=cover.1309457340.git.joe@perches.com \
--to=joe@perches.com \
--cc=jbaron@redhat.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).