From: Randy Dunlap <rdunlap@infradead.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Michael Ellerman <mpe@ellerman.id.au>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: Paul Mackerras <paulus@samba.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] POWERPC: idle: fix return value of __setup handler
Date: Mon, 2 May 2022 12:17:05 -0700 [thread overview]
Message-ID: <067d57b7-f25f-43aa-91a9-297fcadde65b@infradead.org> (raw)
In-Reply-To: <dfe0a791-025b-421f-8cab-9919a50afeb9@csgroup.eu>
On 5/2/22 11:45, Christophe Leroy wrote:
>
>
> Le 02/05/2022 à 17:50, Randy Dunlap a écrit :
>>
>>
>> On 5/2/22 06:19, Michael Ellerman wrote:
>>> Randy Dunlap <rdunlap@infradead.org> writes:
>>>> __setup() handlers should return 1 to obsolete_checksetup() in
>>>> init/main.c to indicate that the boot option has been handled.
>>>> A return of 0 causes the boot option/value to be listed as an Unknown
>>>> kernel parameter and added to init's (limited) argument or environment
>>>> strings. Also, error return codes don't mean anything to
>>>> obsolete_checksetup() -- only non-zero (usually 1) or zero.
>>>> So return 1 from powersave_off().
>>>>
>>>> Fixes: 302eca184fb8 ("[POWERPC] cell: use ppc_md->power_save instead of cbe_idle_loop")
>>>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>>>> From: Igor Zhbanov <i.zhbanov@omprussia.ru>
>>>
>>> What happened here? Is the patch actually from Igor? If so he should be
>>> the author, and it should include his SoB shouldn't it?
>>
>> I don't know what happened. I did the patches.
>> I'll resend them.
>>
>
> Some erroneous copy/paste from
> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220308024228.20477-1-rdunlap@infradead.org/
> ?
Yes, it should have been Reported-by:
>
>> Thanks.
>>
>>> Same comment for "[PATCH] powerpc/4xx: cpm: fix return value of __setup handler".
>>>
>>> cheers
>>>
>>>> Link: lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru
>>>> Cc: Arnd Bergmann <arnd@arndb.de>
>>>> Cc: Paul Mackerras <paulus@samba.org>
>>>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>>>> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>>>> ---
>>>> arch/powerpc/kernel/idle.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> --- linux-next-20220310.orig/arch/powerpc/kernel/idle.c
>>>> +++ linux-next-20220310/arch/powerpc/kernel/idle.c
>>>> @@ -37,7 +37,7 @@ static int __init powersave_off(char *ar
>>>> {
>>>> ppc_md.power_save = NULL;
>>>> cpuidle_disable = IDLE_POWERSAVE_OFF;
>>>> - return 0;
>>>> + return 1;
>>>> }
>>>> __setup("powersave=off", powersave_off);
>>>>
--
~Randy
next prev parent reply other threads:[~2022-05-02 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 6:58 [PATCH] POWERPC: idle: fix return value of __setup handler Randy Dunlap
2022-05-02 13:19 ` Michael Ellerman
2022-05-02 15:50 ` Randy Dunlap
2022-05-02 18:45 ` Christophe Leroy
2022-05-02 19:17 ` Randy Dunlap [this message]
2022-05-03 0:55 ` Michael Ellerman
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=067d57b7-f25f-43aa-91a9-297fcadde65b@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=patches@lists.linux.dev \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).