From: Joe Perches <joe@perches.com>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "John W . Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-wireless@vger.kernel.org,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
Jason Baron <jbaron@redhat.com>,
Jim Cromie <jim.cromie@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] dynamic_debug: introduce debug_hex_dump()
Date: Wed, 14 Nov 2012 09:08:52 -0800 [thread overview]
Message-ID: <1352912932.9388.23.camel@joe-AO722> (raw)
In-Reply-To: <4818336.JicdpLVKSo@lx-vladimir>
On Wed, 2012-11-14 at 18:18 +0200, Vladimir Kondratiev wrote:
> And, here it goes (can I call it PATCH?):
Don't see why not.
> From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
[]
> Introduce debug_hex_dump() that can be dynamically controlled, similar to
> pr_debug.
>
> Also, make print_hex_dump_bytes() dynamically controlled
print_hex_dump_debug might be a better name than
debug_hex_dump because it's more similar to the other
print_hex_dump<_foo> names.
next prev parent reply other threads:[~2012-11-14 17:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 12:17 [RFC] debug_hex_dump() Vladimir Kondratiev
2012-11-14 12:17 ` [RFC] dynamic_debug: introduce debug_hex_dump() Vladimir Kondratiev
2012-11-14 13:41 ` Joe Perches
2012-11-14 16:18 ` Vladimir Kondratiev
2012-11-14 17:08 ` Joe Perches [this message]
2012-11-14 17:27 ` Vladimir Kondratiev
[not found] ` <3304277.iqgq3GH3Yo@lx-vladimir>
2012-11-18 13:51 ` Vladimir Kondratiev
2012-11-18 13:55 ` [PATCH 2/2] dynamic_debug: use constant format in print_hex_dump_bytes() Vladimir Kondratiev
2012-11-18 13:57 ` [PATCH 1/2] dynamic_debug: dynamic hex dump Vladimir Kondratiev
2012-11-18 14:38 ` [RFC] dynamic_debug: introduce debug_hex_dump() Joe Perches
2012-11-18 15:43 ` Vladimir Kondratiev
2012-11-18 17:01 ` Vladimir Kondratiev
2012-11-18 18:35 ` Joe Perches
2012-11-20 16:08 ` Jason Baron
2012-12-04 9:28 ` Vladimir Kondratiev
2012-12-11 19:36 ` Luis R. Rodriguez
2012-12-11 20:08 ` Jason Baron
2012-12-11 20:12 ` Greg KH
2012-12-11 20:24 ` Joe Perches
2012-12-11 22:55 ` Luis R. Rodriguez
2012-12-12 9:12 ` Vladimir Kondratiev
2012-12-12 15:41 ` Luis R. Rodriguez
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=1352912932.9388.23.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@redhat.com \
--cc=jim.cromie@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.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