From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: YueHaibing <yuehaibing@huawei.com>, <benh@kernel.crashing.org>,
<paulus@samba.org>, <robh@kernel.org>,
<gregkh@linuxfoundation.org>, <tglx@linutronix.de>,
<allison@lohutok.net>, <groug@kaod.org>,
<shilpa.bhat@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, YueHaibing <yuehaibing@huawei.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] powerpc/powernv: Make some sysbols static
Date: Thu, 14 Nov 2019 20:07:37 +1100 (AEDT) [thread overview]
Message-ID: <47DFxP5npwz9sPF@ozlabs.org> (raw)
In-Reply-To: <20190702131733.44100-1-yuehaibing@huawei.com>
On Tue, 2019-07-02 at 13:17:33 UTC, YueHaibing wrote:
> Fix sparse warnings:
>
> arch/powerpc/platforms/powernv/opal-psr.c:20:1:
> warning: symbol 'psr_mutex' was not declared. Should it be static?
> arch/powerpc/platforms/powernv/opal-psr.c:27:3:
> warning: symbol 'psr_attrs' was not declared. Should it be static?
> arch/powerpc/platforms/powernv/opal-powercap.c:20:1:
> warning: symbol 'powercap_mutex' was not declared. Should it be static?
> arch/powerpc/platforms/powernv/opal-sensor-groups.c:20:1:
> warning: symbol 'sg_mutex' was not declared. Should it be static?
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/bc75e5438488edef80d952d1146701f872092750
cheers
prev parent reply other threads:[~2019-11-14 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 13:17 [PATCH -next] powerpc/powernv: Make some sysbols static YueHaibing
2019-11-14 9:07 ` Michael Ellerman [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=47DFxP5npwz9sPF@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=allison@lohutok.net \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=groug@kaod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=robh@kernel.org \
--cc=shilpa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).