From: "Zanussi, Tom" <tom.zanussi@linux.intel.com>
To: YueHaibing <yuehaibing@huawei.com>,
rostedt@goodmis.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] tracing: Make two symbols static
Date: Fri, 14 Jun 2019 14:58:50 -0500 [thread overview]
Message-ID: <8c64a9e1-03c5-8716-9151-23fc5f5f645c@linux.intel.com> (raw)
In-Reply-To: <20190614153210.24424-1-yuehaibing@huawei.com>
Hi YueHaibing,
On 6/14/2019 10:32 AM, YueHaibing wrote:
> Fix sparse warnings:
>
> kernel/trace/trace.c:6927:24: warning:
> symbol 'get_tracing_log_err' was not declared. Should it be static?
> kernel/trace/trace.c:8196:15: warning:
> symbol 'trace_instance_dir' was not declared. Should it be static?
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
These look fine to me.
Acked-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Thanks,
Tom
> ---
> kernel/trace/trace.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index a092e40..650b141 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -6924,7 +6924,7 @@ struct tracing_log_err {
>
> static DEFINE_MUTEX(tracing_err_log_lock);
>
> -struct tracing_log_err *get_tracing_log_err(struct trace_array *tr)
> +static struct tracing_log_err *get_tracing_log_err(struct trace_array *tr)
> {
> struct tracing_log_err *err;
>
> @@ -8193,7 +8193,7 @@ static const struct file_operations buffer_percent_fops = {
> .llseek = default_llseek,
> };
>
> -struct dentry *trace_instance_dir;
> +static struct dentry *trace_instance_dir;
>
> static void
> init_tracer_tracefs(struct trace_array *tr, struct dentry *d_tracer);
prev parent reply other threads:[~2019-06-14 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 15:32 YueHaibing
2019-06-14 19:58 ` Zanussi, Tom [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=8c64a9e1-03c5-8716-9151-23fc5f5f645c@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®