From: Joe Perches <joe@perches.com>
To: alexandrasava18@gmail.com
Cc: gregkh@linuxfoundation.org, pavan_savoy@ti.com,
mgherzan@gmail.com, daniel.baluta@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] Enhance logging for Shared Transport - TI driver
Date: Fri, 16 Mar 2012 11:06:43 -0700 [thread overview]
Message-ID: <1331921203.11368.4.camel@joe2Laptop> (raw)
In-Reply-To: <9ea802684dee3b531a19f93424c77e22a955dd54.1331920050.git.alexandrasava18@gmail.com>
On Fri, 2012-03-16 at 19:58 +0200, alexandrasava18@gmail.com wrote:
> From: Alexandra Sava <alexandrasava18@gmail.com>
> * reduced verbosity
> * replaced pr_* with dev_* where possible
pr_<level> and dev_<level> formats should end in with
a "\n" newline.
> diff --git a/drivers/misc/ti-st/st_core.c b/drivers/misc/ti-st/st_core.c
[]
> @@ -19,7 +19,6 @@
> *
> */
>
> -#define pr_fmt(fmt) "(stc): " fmt
It'd be useful to keep the #define pr_fmt
perhaps as
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
for each file so that the pr_<level> uses
are prefixed by subsystem.
> @@ -122,12 +119,12 @@ void st_send_frame(unsigned char chnl_id, struct st_data_s *st_gdata)
> (st_gdata->list[chnl_id]->recv
> (st_gdata->list[chnl_id]->priv_data, st_gdata->rx_skb)
> != 0)) {
> - pr_err(" proto stack %d's ->recv failed", chnl_id);
> + pr_err("proto stack %d's ->recv failed", chnl_id);
pr_err(proto stack %d's ->recv failed\n", chnl_id);
> kfree_skb(st_gdata->rx_skb);
> return;
> }
> } else {
> - pr_err(" proto stack %d's ->recv null", chnl_id);
> + pr_err("proto stack %d's ->recv null", chnl_id);
pr_err("proto stack %d's ->recv null\n", chnl_id);
etc...
next prev parent reply other threads:[~2012-03-16 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 17:58 [PATCH V2] Enhance logging for Shared Transport - TI driver alexandrasava18
2012-03-16 18:06 ` Joe Perches [this message]
2012-03-16 21:14 ` Mircea Gherzan
2012-03-16 21:23 ` Mircea Gherzan
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=1331921203.11368.4.camel@joe2Laptop \
--to=joe@perches.com \
--cc=alexandrasava18@gmail.com \
--cc=daniel.baluta@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgherzan@gmail.com \
--cc=pavan_savoy@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.