From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: romieu@fr.zoreil.com, sorbica@icplus.com.tw,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ipg: Use current logging styles
Date: Mon, 01 Aug 2011 01:57:18 -0700 (PDT) [thread overview]
Message-ID: <20110801.015718.1883456310806281501.davem@davemloft.net> (raw)
In-Reply-To: <2ee87bfccbbb5cf1776df6751b65e4a3110019f4.1311993468.git.joe@perches.com>
From: Joe Perches <joe@perches.com>
Date: Fri, 29 Jul 2011 19:38:14 -0700
> Add and use pr_fmt, pr_<level> and netdev_<level>.
> Convert printks with %[n].[n]x to %nx to be shorter
> and clearer.
> Consolidate printks to use a single printk rather
> than continued printks without KERN_CONT.
> Removed unnecessary trailing periods.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Queued up for net-next
prev parent reply other threads:[~2011-08-01 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 2:38 [PATCH 1/2] ipg: Use current logging styles Joe Perches
2011-07-30 2:38 ` [PATCH 2/2] ipg: Use const Joe Perches
2011-08-01 8:57 ` David Miller
2011-08-01 8:57 ` 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=20110801.015718.1883456310806281501.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=sorbica@icplus.com.tw \
/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).