[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z4Jdum7jgDg7EzDa@alpha.franken.de>
Date: Sat, 11 Jan 2025 13:02:02 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Thorsten Blum <thorsten.blum@...ux.dev>
Cc: Jiaxun Yang <jiaxun.yang@...goat.com>,
Gregory CLEMENT <gregory.clement@...tlin.com>,
Huang Pei <huangpei@...ngson.cn>,
Vladimir Kondratiev <vladimir.kondratiev@...el.com>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: traps: Use str_enabled_disabled() in
parity_protection_init()
On Thu, Jan 09, 2025 at 10:55:23PM +0100, Thorsten Blum wrote:
> Remove hard-coded strings by using the str_enabled_disabled() helper
> function.
>
> Use pr_info() instead of printk(KERN_INFO) to silence multiple
> checkpatch warnings.
>
> Suggested-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>
> Signed-off-by: Thorsten Blum <thorsten.blum@...ux.dev>
> ---
> arch/mips/kernel/traps.c | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists