From: Choi Gi-yong <yong@gnoy.org>
To: joe@perches.com
Cc: tj@kernel.org, linux-kernel@vger.kernel.org,
Choi Gi-yong <yong@gnoy.org>
Subject: [PATCH 2/2] mm: Changed pr_warning() to pr_warn()
Date: Sun, 9 Mar 2014 17:15:00 +0900 [thread overview]
Message-ID: <1394352900-13629-1-git-send-email-yong@gnoy.org> (raw)
Signed-off-by: Choi Gi-yong <yong@gnoy.org>
---
mm/percpu.c | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/mm/percpu.c b/mm/percpu.c
index ff6cce2..061f312 100644
--- a/mm/percpu.c
+++ b/mm/percpu.c
@@ -812,8 +812,8 @@ fail_unlock:
fail_unlock_mutex:
mutex_unlock(&pcpu_alloc_mutex);
if (warn_limit) {
- pr_warn("PERCPU: allocation failed, size=%zu align=%zu, "
- "%s\n", size, align, err);
+ pr_warn("PERCPU: allocation failed, size=%zu align=%zu, %s\n",
+ size, align, err);
dump_stack();
if (!--warn_limit)
pr_info("PERCPU: limit reached, disable warning\n");
@@ -1689,9 +1689,8 @@ int __init pcpu_embed_first_chunk(size_t reserved_size, size_t dyn_size,
/* warn if maximum distance is further than 75% of vmalloc space */
if (max_distance > VMALLOC_TOTAL * 3 / 4) {
- pr_warn("PERCPU: max_distance=0x%zx too large for vmalloc "
- "space 0x%lx\n", max_distance,
- VMALLOC_TOTAL);
+ pr_warn("PERCPU: max_distance=0x%zx too large for vmalloc space 0x%lx\n",
+ max_distance, VMALLOC_TOTAL);
#ifdef CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK
/* and fail if we have fallback */
rc = -EINVAL;
@@ -1773,8 +1772,8 @@ int __init pcpu_page_first_chunk(size_t reserved_size,
ptr = alloc_fn(cpu, PAGE_SIZE, PAGE_SIZE);
if (!ptr) {
- pr_warn("PERCPU: failed to allocate %s page "
- "for cpu%u\n", psize_str, cpu);
+ pr_warn("PERCPU: failed to allocate %s page for cpu%u\n",
+ psize_str, cpu);
goto enomem;
}
/* kmemleak tracks the percpu allocations separately */
--
1.8.3.2
next reply other threads:[~2014-03-09 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 8:15 Choi Gi-yong [this message]
2014-03-09 22:15 ` Joe Perches
2014-03-13 0:33 ` 최(Choi)기용(Gi-yong)
-- strict thread matches above, loose matches on Subject: below --
2014-03-08 3:51 Choi Gi-yong
2014-03-08 4:00 ` 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=1394352900-13629-1-git-send-email-yong@gnoy.org \
--to=yong@gnoy.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®