From: David Cohen <david.a.cohen@linux.intel.com>
To: ohad@wizery.com
Cc: linux-kernel@vger.kernel.org,
Jocelyn Falempe <jocelyn.falempe@intel.com>
Subject: Re: [PATCH] rpmsg: reduce rpmsg_virtio verbosity
Date: Tue, 12 Nov 2013 13:48:18 -0800 [thread overview]
Message-ID: <5282A222.5020702@linux.intel.com> (raw)
In-Reply-To: <525EBBAA.9000209@linux.intel.com>
Hi,
On 10/16/2013 09:15 AM, David Cohen wrote:
> On 10/03/2013 11:36 AM, David Cohen wrote:
>> From: Jocelyn Falempe <jocelyn.falempe@intel.com>
>>
>> rpmsg_virtio TX/RX messages are very verbose, overflowing kernel printk
>> buffer. This patch makes the guilty print_hex_dump()'s to act as
>> dev_dbg() and do nothing in case neither DEBUG nor CONFIG_DYNAMIC_DEBUG
>> are defined.
>>
>> Signed-off-by: Jocelyn Falempe <jocelyn.falempe@intel.com>
>> Signed-off-by: David Cohen <david.a.cohen@linux.intel.com>
>> ---
>
> Ping :)
> Comments here?
Ping again :)
>
> Br, David Cohen
>
next prev parent reply other threads:[~2013-11-12 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 18:36 [PATCH] rpmsg: reduce rpmsg_virtio verbosity David Cohen
2013-10-16 16:15 ` David Cohen
2013-11-12 21:48 ` David Cohen [this message]
2014-02-24 15:11 ` Ohad Ben-Cohen
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=5282A222.5020702@linux.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=jocelyn.falempe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.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