From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Aboorva Devarajan <aboorvad@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] powerpc/powernv: Avoid strlen() in pnv_restart()
Date: Fri, 31 Jul 2026 09:14:01 +0200 [thread overview]
Message-ID: <2c505334-a744-499f-88f5-d2c779f69f0f@kernel.org> (raw)
In-Reply-To: <20260721155346.121975-3-thorsten.blum@linux.dev>
Le 21/07/2026 à 17:53, Thorsten Blum a écrit :
> Check only the first byte instead of scanning the entire string with
> strlen().
Well, strlen() is not going to scan the entire string, it will break at
first 0. But I agreed calling strlen() is not worth it.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
Reviewed-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
> ---
> arch/powerpc/platforms/powernv/setup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/platforms/powernv/setup.c b/arch/powerpc/platforms/powernv/setup.c
> index 06ed5e2aa265..2af92e7ba4ee 100644
> --- a/arch/powerpc/platforms/powernv/setup.c
> +++ b/arch/powerpc/platforms/powernv/setup.c
> @@ -312,7 +312,7 @@ static void __noreturn pnv_restart(char *cmd)
> pnv_prepare_going_down();
>
> do {
> - if (!cmd || !strlen(cmd))
> + if (!cmd || *cmd == '\0')
Maybe !*cmd instead ?
> rc = opal_cec_reboot();
> else if (strcmp(cmd, "full") == 0)
> rc = opal_cec_reboot2(OPAL_REBOOT_FULL_IPL, NULL);
prev parent reply other threads:[~2026-07-31 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 15:53 [PATCH 1/2] powerpc/powernv: Avoid strlen() in pnv_restart() Thorsten Blum
2026-07-21 15:53 ` [PATCH 2/2] powerpc/pseries: Avoid strlen() in do_{remove,update}_property() Thorsten Blum
2026-07-31 7:15 ` Christophe Leroy (CS GROUP)
2026-07-31 7:14 ` Christophe Leroy (CS GROUP) [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=2c505334-a744-499f-88f5-d2c779f69f0f@kernel.org \
--to=chleroy@kernel.org \
--cc=aboorvad@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--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