From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Joe Perches <joe@perches.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
Jon Maloy <jon.maloy@ericsson.com>,
Erik Hugne <erik.hugne@ericsson.com>, <ying.xue@windriver.com>
Subject: Re: [PATCH net-next] tipc: Use pr_fmt
Date: Fri, 13 Jul 2012 11:45:44 -0400 [thread overview]
Message-ID: <20120713154544.GA31280@windriver.com> (raw)
In-Reply-To: <1342115481.13046.5.camel@joe2Laptop>
[[PATCH net-next] tipc: Use pr_fmt] On 12/07/2012 (Thu 10:51) Joe Perches wrote:
[...]
>
> How about extending this to use the more common pr_fmt prefix?
We can probably do that. I'll incorporate that into the 3/8 patch,
rather than have two similar patches in the series, with the 2nd just
going in and touching all the same lines a second time.
Thanks,
Paul.
next prev parent reply other threads:[~2012-07-13 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 16:39 [PATCH net-next 0/8] tipc: kill off struct print_buf/log Paul Gortmaker
2012-07-12 16:39 ` [PATCH net-next 1/8] tipc: factor stats struct out of the larger link struct Paul Gortmaker
2012-07-12 16:39 ` [PATCH net-next 2/8] tipc: limit error messages relating to memory leak to one line Paul Gortmaker
2012-07-12 16:39 ` [PATCH net-next 3/8] tipc: use standard printk shortcut macros (pr_err etc.) Paul Gortmaker
2012-07-13 23:53 ` [PATCH net-next v2 " Paul Gortmaker
2012-07-12 16:39 ` [PATCH net-next 4/8] tipc: remove TIPC packet debugging functions and macros Paul Gortmaker
2012-07-12 16:39 ` [PATCH net-next 5/8] tipc: simplify link_print by divorcing it from using tipc_printf Paul Gortmaker
2012-07-12 16:39 ` [PATCH net-next 6/8] tipc: simplify print buffer handling in tipc_printf Paul Gortmaker
2012-07-12 16:40 ` [PATCH net-next 7/8] tipc: phase out most of the struct print_buf usage Paul Gortmaker
2012-07-12 16:40 ` [PATCH net-next 8/8] tipc: remove print_buf and deprecated log buffer code Paul Gortmaker
2012-07-12 17:51 ` [PATCH net-next] tipc: Use pr_fmt Joe Perches
2012-07-13 15:45 ` Paul Gortmaker [this message]
2012-07-13 19:04 ` Joe Perches
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=20120713154544.GA31280@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=joe@perches.com \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=ying.xue@windriver.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.