From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Huang Pei <huangpei@loongson.cn>,
Vladimir Kondratiev <vladimir.kondratiev@intel.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: traps: Use str_enabled_disabled() in parity_protection_init()
Date: Sat, 11 Jan 2025 13:02:02 +0100 [thread overview]
Message-ID: <Z4Jdum7jgDg7EzDa@alpha.franken.de> (raw)
In-Reply-To: <20250109215524.195008-2-thorsten.blum@linux.dev>
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@wanadoo.fr>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.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 ]
prev parent reply other threads:[~2025-01-11 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 21:55 [PATCH] MIPS: traps: Use str_enabled_disabled() in parity_protection_init() Thorsten Blum
2025-01-10 8:09 ` Philippe Mathieu-Daudé
2025-01-11 12:02 ` Thomas Bogendoerfer [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=Z4Jdum7jgDg7EzDa@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gregory.clement@bootlin.com \
--cc=huangpei@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=vladimir.kondratiev@intel.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