From: Mitchel Humpherys <mitchelh@codeaurora.org>
To: Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Joe Perches <joe@perches.com>,
linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
Mitchel Humpherys <mitchelh@codeaurora.org>
Subject: [PATCH v2] Some printk cleanup in mm
Date: Thu, 27 Mar 2014 10:54:18 -0700 [thread overview]
Message-ID: <1395942859-11611-1-git-send-email-mitchelh@codeaurora.org> (raw)
This series cleans up some printks in the mm code that were missing
log levels.
Changelog:
- v2: Suggestions by Joe Perches (pr_fmt, pr_cont, pr_err, __func__,
missing \n)
Mitchel Humpherys (1):
mm: convert some level-less printks to pr_*
mm/bounce.c | 7 +++++--
mm/mempolicy.c | 5 ++++-
mm/mmap.c | 21 ++++++++++++---------
mm/nommu.c | 5 ++++-
mm/slub.c | 9 ++++++---
mm/vmscan.c | 5 ++++-
6 files changed, 35 insertions(+), 17 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Mitchel Humpherys <mitchelh@codeaurora.org>
To: Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Joe Perches <joe@perches.com>,
linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
Mitchel Humpherys <mitchelh@codeaurora.org>
Subject: [PATCH v2] Some printk cleanup in mm
Date: Thu, 27 Mar 2014 10:54:18 -0700 [thread overview]
Message-ID: <1395942859-11611-1-git-send-email-mitchelh@codeaurora.org> (raw)
This series cleans up some printks in the mm code that were missing
log levels.
Changelog:
- v2: Suggestions by Joe Perches (pr_fmt, pr_cont, pr_err, __func__,
missing \n)
Mitchel Humpherys (1):
mm: convert some level-less printks to pr_*
mm/bounce.c | 7 +++++--
mm/mempolicy.c | 5 ++++-
mm/mmap.c | 21 ++++++++++++---------
mm/nommu.c | 5 ++++-
mm/slub.c | 9 ++++++---
mm/vmscan.c | 5 ++++-
6 files changed, 35 insertions(+), 17 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-03-27 17:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 17:54 Mitchel Humpherys [this message]
2014-03-27 17:54 ` [PATCH v2] Some printk cleanup in mm Mitchel Humpherys
2014-03-27 17:54 ` [PATCH v2] mm: convert some level-less printks to pr_* Mitchel Humpherys
2014-03-27 17:54 ` Mitchel Humpherys
2014-03-31 18:35 ` Christoph Lameter
2014-03-31 18:35 ` Christoph Lameter
2014-03-31 18:44 ` Joe Perches
2014-03-31 18:44 ` Joe Perches
2014-04-03 16:33 ` Christoph Lameter
2014-04-03 16:33 ` Christoph Lameter
2014-04-03 16:57 ` Mitchel Humpherys
2014-04-03 16:57 ` Mitchel Humpherys
2014-04-14 22:55 ` Andrew Morton
2014-04-14 22:55 ` Andrew Morton
2014-04-15 23:58 ` Mitchel Humpherys
2014-04-15 23:58 ` Mitchel Humpherys
2014-04-16 0:05 ` Mitchel Humpherys
2014-04-16 0:05 ` Mitchel Humpherys
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=1395942859-11611-1-git-send-email-mitchelh@codeaurora.org \
--to=mitchelh@codeaurora.org \
--cc=cl@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.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 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.