From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Malaterre <malat@debian.org>
Cc: Chunyan Zhang <zhang.chunyan@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: make function ‘ftrace_exports’ static
Date: Thu, 20 Dec 2018 09:33:13 -0500 [thread overview]
Message-ID: <20181220093313.16b227fd@gandalf.local.home> (raw)
In-Reply-To: <20180516193012.25390-1-malat@debian.org>
Cleaning out my INBOX, I stumbled on this patch that slipped through
the cracks. Applied to my local queue.
Thanks, and sorry for the delay.
-- Steve
On Wed, 16 May 2018 21:30:12 +0200
Mathieu Malaterre <malat@debian.org> wrote:
> In commit 478409dd683d ("tracing: Add hook to function tracing for other
> subsystems to use"), a new function ‘ftrace_exports’ was added. Since
> this function can be made static, make it so.
>
> Silence the following warning triggered using W=1:
>
> kernel/trace/trace.c:2451:6: warning: no previous prototype for ‘ftrace_exports’ [-Wmissing-prototypes]
>
> Signed-off-by: Mathieu Malaterre <malat@debian.org>
> ---
> kernel/trace/trace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 414d7210b2ec..76b96f453cf7 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -2448,7 +2448,7 @@ static inline void ftrace_exports_disable(void)
> static_branch_disable(&ftrace_exports_enabled);
> }
>
> -void ftrace_exports(struct ring_buffer_event *event)
> +static void ftrace_exports(struct ring_buffer_event *event)
> {
> struct trace_export *export;
>
prev parent reply other threads:[~2018-12-20 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 19:30 Mathieu Malaterre
2018-12-20 14:33 ` Steven Rostedt [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=20181220093313.16b227fd@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malat@debian.org \
--cc=mingo@redhat.com \
--cc=zhang.chunyan@linaro.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
all inboxes | Powered by JetHome®