From: Vipin K Parashar <vipin@linux.vnet.ibm.com>
To: Christophe LEROY <christophe.leroy@c-s.fr>,
linuxppc-dev@lists.ozlabs.org
Cc: nfont@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/numa: Correct kernel message severity
Date: Wed, 14 Mar 2018 13:23:55 +0530 [thread overview]
Message-ID: <c37aba4b-b4b9-e9b5-b36a-13bd594606b8@linux.vnet.ibm.com> (raw)
In-Reply-To: <29183547-d1c5-5282-86cb-3d5acbade58f@c-s.fr>
On Tuesday 13 March 2018 03:58 PM, Christophe LEROY wrote:
>
>
> Le 13/03/2018 à 11:11, Vipin K Parashar a écrit :
>> printk in unmap_cpu_from_node() uses KERN_ERR message severity
>> for a WARNING message. Correct message severity to KERN_WARNING.
>>
>> Signed-off-by: Vipin K Parashar <vipin@linux.vnet.ibm.com>
>> ---
>> arch/powerpc/mm/numa.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
>> index edd8d0b..79c94cc 100644
>> --- a/arch/powerpc/mm/numa.c
>> +++ b/arch/powerpc/mm/numa.c
>> @@ -163,7 +163,7 @@ static void unmap_cpu_from_node(unsigned long cpu)
>> if (cpumask_test_cpu(cpu, node_to_cpumask_map[node])) {
>> cpumask_clear_cpu(cpu, node_to_cpumask_map[node]);
>> } else {
>> - printk(KERN_ERR "WARNING: cpu %lu not found in node %d\n",
>> + printk(KERN_WARNING "WARNING: cpu %lu not found in node %d\n",
> > cpu, node);
>
> Why not take the opportunity to use pr_warn() instead, hence to put
> back the cpu and node vars on the same line.
>
> Christophe
>
Yes, Thanks!!
Send v2.
>> }
>> }
>>
>
prev parent reply other threads:[~2018-03-14 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 10:11 [PATCH] powerpc/numa: Correct kernel message severity Vipin K Parashar
2018-03-13 10:28 ` Christophe LEROY
2018-03-14 7:53 ` Vipin K Parashar [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=c37aba4b-b4b9-e9b5-b36a-13bd594606b8@linux.vnet.ibm.com \
--to=vipin@linux.vnet.ibm.com \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
/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