From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Colin King <colin.king@canonical.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>, Scott Wood <oss@buserror.net>,
Kevin Hao <haokexin@gmail.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/32: add missing \n at end of printk warning message
Date: Tue, 13 Sep 2016 11:25:58 +1000 [thread overview]
Message-ID: <87sht4pp3t.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <fcc50e93-5009-496d-3251-b2d7ef820224@c-s.fr>
Christophe Leroy <christophe.leroy@c-s.fr> writes:
> Le 12/09/2016 à 12:12, Colin King a écrit :
>> diff --git a/arch/powerpc/mm/init_32.c b/arch/powerpc/mm/init_32.c
>> index 448685f..b532dd9 100644
>> --- a/arch/powerpc/mm/init_32.c
>> +++ b/arch/powerpc/mm/init_32.c
>> @@ -137,7 +137,7 @@ void __init MMU_init(void)
>> if (memblock.memory.cnt > 1) {
>> #ifndef CONFIG_WII
>> memblock_enforce_memory_limit(memblock.memory.regions[0].size);
>> - printk(KERN_WARNING "Only using first contiguous memory region");
>> + printk(KERN_WARNING "Only using first contiguous memory region\n");
>
> This line was already 81 characters long. It is now 83.
That doesn't really bother me.
> I would suggest to use pr_warn() instead in order to shorten the line.
But I do like pr_warn(), it's less shouty.
I'll fix it up when I apply it.
cheers
next prev parent reply other threads:[~2016-09-13 1:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 10:12 Colin King
2016-09-12 15:21 ` Christophe Leroy
2016-09-13 1:25 ` Michael Ellerman [this message]
2016-09-12 16:34 ` Joe Perches
2016-09-12 16:49 ` Colin Ian King
2016-09-13 12:16 ` Michael Ellerman
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=87sht4pp3t.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=colin.king@canonical.com \
--cc=haokexin@gmail.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=paulus@samba.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®