From: Mike Travis <mike.travis@hpe.com>
To: Colin King <colin.king@canonical.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
"maintainer:X86" <x86@kernel.org>,
Russ Anderson <russ.anderson@hpe.com>,
"travis @ sgi . com" <travis@sgi.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/platform/UV: make functions uv_handle_nmi and uv_nmi_setup_common static
Date: Wed, 06 Dec 2017 17:38:48 +0000 [thread overview]
Message-ID: <c97ea55b-e941-546d-9501-d882290638cd@hpe.com> (raw)
In-Reply-To: <20171206170828.23524-1-colin.king@canonical.com>
I know you've already changed it but the UV changes look
fine, so ACK for that. Thanks.
On 12/6/2017 9:08 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Functions uv_handle_nmi and uv_nmi_setup_common are local to the
> source and do not need to be in global scope, so make them static.
>
> Cleans up sparse warnings:
> symbol 'uv_handle_nmi' was not declared. Should it be static?
> symbol 'uv_nmi_setup_common' was not declared. Should it be static?
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> arch/x86/platform/uv/uv_nmi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/platform/uv/uv_nmi.c b/arch/x86/platform/uv/uv_nmi.c
> index c34bd8233f7c..5f64f30873e2 100644
> --- a/arch/x86/platform/uv/uv_nmi.c
> +++ b/arch/x86/platform/uv/uv_nmi.c
> @@ -905,7 +905,7 @@ static inline void uv_call_kgdb_kdb(int cpu, struct pt_regs *regs, int master)
> /*
> * UV NMI handler
> */
> -int uv_handle_nmi(unsigned int reason, struct pt_regs *regs)
> +static int uv_handle_nmi(unsigned int reason, struct pt_regs *regs)
> {
> struct uv_hub_nmi_s *hub_nmi = uv_hub_nmi;
> int cpu = smp_processor_id();
> @@ -1013,7 +1013,7 @@ void uv_nmi_init(void)
> }
>
> /* Setup HUB NMI info */
> -void __init uv_nmi_setup_common(bool hubbed)
> +static void __init uv_nmi_setup_common(bool hubbed)
> {
> int size = sizeof(void *) * (1 << NODES_SHIFT);
> int cpu;
>
prev parent reply other threads:[~2017-12-06 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 17:08 [PATCH] x86/platform/UV: make functions uv_handle_nmi and uv_nmi_setup_common static Colin King
2017-12-06 17:15 ` Ingo Molnar
2017-12-06 17:38 ` Mike Travis [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=c97ea55b-e941-546d-9501-d882290638cd@hpe.com \
--to=mike.travis@hpe.com \
--cc=colin.king@canonical.com \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=russ.anderson@hpe.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@kernel.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