From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Jason Yan <yanaijie@huawei.com>
Cc: suzuki.poulose@arm.com, alexander.shishkin@linux.intel.com,
linux-kernel@vger.kernel.org, Hulk Robot <hulkci@huawei.com>,
linux-arm-kernel@lists.infradead.org, mike.leach@linaro.org
Subject: Re: [PATCH] coresight: cti: make some symbols static
Date: Mon, 13 Apr 2020 11:58:37 -0600 [thread overview]
Message-ID: <20200413175837.GE28804@xps15> (raw)
In-Reply-To: <20200413082224.23090-1-yanaijie@huawei.com>
On Mon, Apr 13, 2020 at 04:22:24PM +0800, Jason Yan wrote:
> Fix the following sparse warning:
>
> drivers/hwtracing/coresight/coresight-cti.c:22:1: warning: symbol
> 'ect_net' was not declared. Should it be static?
> drivers/hwtracing/coresight/coresight-cti.c:625:32: warning: symbol
> 'cti_ops_ect' was not declared. Should it be static?
> drivers/hwtracing/coresight/coresight-cti.c:630:28: warning: symbol
> 'cti_ops' was not declared. Should it be static?
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> ---
> drivers/hwtracing/coresight/coresight-cti.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/hwtracing/coresight/coresight-cti.c b/drivers/hwtracing/coresight/coresight-cti.c
> index 9e262f5a85e3..7fc1fc8d7738 100644
> --- a/drivers/hwtracing/coresight/coresight-cti.c
> +++ b/drivers/hwtracing/coresight/coresight-cti.c
> @@ -19,7 +19,7 @@
> */
>
> /* net of CTI devices connected via CTM */
> -LIST_HEAD(ect_net);
> +static LIST_HEAD(ect_net);
>
> /* protect the list */
> static DEFINE_MUTEX(ect_mutex);
> @@ -622,12 +622,12 @@ int cti_disable(struct coresight_device *csdev)
> return cti_disable_hw(drvdata);
> }
>
> -const struct coresight_ops_ect cti_ops_ect = {
> +static const struct coresight_ops_ect cti_ops_ect = {
> .enable = cti_enable,
> .disable = cti_disable,
> };
>
> -const struct coresight_ops cti_ops = {
> +static const struct coresight_ops cti_ops = {
> .ect_ops = &cti_ops_ect,
> };
Applied - thanks,
Mathieu
>
> --
> 2.21.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-04-13 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 8:22 [PATCH] coresight: cti: make some symbols static Jason Yan
2020-04-13 17:58 ` Mathieu Poirier [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=20200413175837.GE28804@xps15 \
--to=mathieu.poirier@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=hulkci@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=yanaijie@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