From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Loongson64: env: Use str_on_off() helper in prom_lefi_init_env()
Date: Mon, 20 Jan 2025 20:41:28 +0100 [thread overview]
Message-ID: <Z46m6MHmRMfUnVrD@alpha.franken.de> (raw)
In-Reply-To: <20250115090134.918023-2-thorsten.blum@linux.dev>
On Wed, Jan 15, 2025 at 10:01:35AM +0100, Thorsten Blum wrote:
> Remove hard-coded strings by using the str_on_off() helper function.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> arch/mips/loongson64/env.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/mips/loongson64/env.c b/arch/mips/loongson64/env.c
> index 09ff05269861..be8d2ad10750 100644
> --- a/arch/mips/loongson64/env.c
> +++ b/arch/mips/loongson64/env.c
> @@ -17,6 +17,7 @@
> #include <linux/dma-map-ops.h>
> #include <linux/export.h>
> #include <linux/pci_ids.h>
> +#include <linux/string_choices.h>
> #include <asm/bootinfo.h>
> #include <loongson.h>
> #include <boot_param.h>
> @@ -162,7 +163,7 @@ void __init prom_lefi_init_env(void)
> dma_default_coherent = !eirq_source->dma_noncoherent;
> }
>
> - pr_info("Firmware: Coherent DMA: %s\n", dma_default_coherent ? "on" : "off");
> + pr_info("Firmware: Coherent DMA: %s\n", str_on_off(dma_default_coherent));
>
> loongson_sysconf.restart_addr = boot_p->reset_system.ResetWarm;
> loongson_sysconf.poweroff_addr = boot_p->reset_system.Shutdown;
> --
> 2.47.1
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-20 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 9:01 [PATCH] MIPS: Loongson64: env: Use str_on_off() helper in prom_lefi_init_env() Thorsten Blum
2025-01-20 19:41 ` 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=Z46m6MHmRMfUnVrD@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
/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