From: Ingo Molnar <mingo@kernel.org>
To: He Ying <heying24@huawei.com>
Cc: peterz@infradead.org, frederic@kernel.org, paulmck@kernel.org,
christophe.leroy@csgroup.eu, clg@kaod.org, qais.yousef@arm.com,
johnny.chenyi@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] smp: kernel/panic.c - silence warnings
Date: Wed, 17 Mar 2021 10:49:08 +0100 [thread overview]
Message-ID: <20210317094908.GB1724119@gmail.com> (raw)
In-Reply-To: <20210316084150.75201-1-heying24@huawei.com>
* He Ying <heying24@huawei.com> wrote:
> We found these warnings in kernel/panic.c by using sparse tool:
> warning: symbol 'panic_smp_self_stop' was not declared.
> warning: symbol 'nmi_panic_self_stop' was not declared.
> warning: symbol 'crash_smp_send_stop' was not declared.
>
> To avoid them, add declarations for these three functions in
> include/linux/smp.h.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: He Ying <heying24@huawei.com>
> ---
> V1->V2:
> - fix some misspellings
>
> include/linux/smp.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/include/linux/smp.h b/include/linux/smp.h
> index 70c6f6284dcf..27008a1c8111 100644
> --- a/include/linux/smp.h
> +++ b/include/linux/smp.h
> @@ -50,6 +50,14 @@ extern unsigned int total_cpus;
> int smp_call_function_single(int cpuid, smp_call_func_t func, void *info,
> int wait);
>
> +/*
> + * Cpus stopping functions in panic. All have default weak definitions.
> + * Architecture-dependent code may override them.
> + */
> +void panic_smp_self_stop(void);
> +void nmi_panic_self_stop(struct pt_regs *regs);
> +void crash_smp_send_stop(void);
Please follow the 'extern' convention used for prototype declarations
in that header file.
Thanks,
Ingo
next prev parent reply other threads:[~2021-03-17 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 8:41 [PATCH v2] smp: kernel/panic.c - silence warnings He Ying
2021-03-17 9:49 ` Ingo Molnar [this message]
2021-03-17 11:00 ` Christophe Leroy
2021-03-17 12:23 ` Peter Zijlstra
2021-03-17 17:17 ` Christophe Leroy
2021-03-17 17:37 ` Peter Zijlstra
2021-03-17 20:09 ` Ingo Molnar
2021-03-18 2:56 ` heying (H)
2021-03-18 6:11 ` Christophe Leroy
2021-03-18 6:04 ` Christophe Leroy
2021-03-18 5:53 ` Christophe Leroy
2021-03-19 1:39 ` heying (H)
2021-03-19 6:58 ` Christophe Leroy
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=20210317094908.GB1724119@gmail.com \
--to=mingo@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=frederic@kernel.org \
--cc=heying24@huawei.com \
--cc=johnny.chenyi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.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