From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: sjur.brandeland@stericsson.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/caif: Use pr_fmt
Date: Mon, 06 Sep 2010 18:40:30 -0700 (PDT) [thread overview]
Message-ID: <20100906.184030.91320907.davem@davemloft.net> (raw)
In-Reply-To: <1283758271.23280.73.camel@Joe-Laptop>
From: Joe Perches <joe@perches.com>
Date: Mon, 06 Sep 2010 00:31:11 -0700
> This patch standardizes caif message logging prefixes.
>
> Add #define pr_fmt(fmt) KBUILD_MODNAME ":%s(): " fmt, __func__
> Add missing "\n"s to some logging messages
> Convert pr_warning to pr_warn
>
> This changes the logging message prefix from CAIF: to caif:
> for all uses but caif_socket.c and chnl_net.c. Those now use
> their filename without extension.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Applied.
prev parent reply other threads:[~2010-09-07 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 7:31 [PATCH net-next] net/caif: Use pr_fmt Joe Perches
2010-09-06 8:08 ` [PATCH net-next] net/caifcaif_dev.c: Use netdev_<level> Joe Perches
2010-09-07 1:40 ` David Miller
2010-09-07 1:40 ` David Miller [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=20100906.184030.91320907.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sjur.brandeland@stericsson.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;
as well as URLs for NNTP newsgroup(s).