From: Tejun Heo <tj@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] mm: percpu: Use pr_fmt to prefix output
Date: Fri, 4 Mar 2016 07:43:31 -0500 [thread overview]
Message-ID: <20160304124331.GD13868@htj.duckdns.org> (raw)
In-Reply-To: <ddb59cbebc26211964c1e45d3d4251d76ae851ab.1457047399.git.joe@perches.com>
On Thu, Mar 03, 2016 at 03:25:34PM -0800, Joe Perches wrote:
> Use the normal mechanism to make the logging output consistently
> "percpu: " instead of a mix of "PERCPU: " and "percpu: "
>
> Signed-off-by: Joe Perches <joe@perches.com>
Acked-by: Tejun Heo <tj@kernel.org>
Andrew, I think it'd be best to route this one with the rest of the
series through -mm.
Thanks!
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-03-04 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 23:25 [PATCH 0/4] mm: Make the logging a bit more consistent Joe Perches
2016-03-03 23:25 ` [PATCH 1/4] mm: Convert pr_warning to pr_warn Joe Perches
2016-03-04 12:41 ` Tejun Heo
2016-03-03 23:25 ` [PATCH 2/4] mm: Coalesce split strings Joe Perches
2016-03-04 12:41 ` Tejun Heo
2016-03-03 23:25 ` [PATCH 3/4] mm: Convert printk(KERN_<LEVEL> to pr_<level> Joe Perches
2016-03-04 12:42 ` Tejun Heo
2016-03-03 23:25 ` [PATCH 4/4] mm: percpu: Use pr_fmt to prefix output Joe Perches
2016-03-04 12:43 ` Tejun Heo [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=20160304124331.GD13868@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).