From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Viktor Rosendahl (BMW)" <viktor.rosendahl@gmail.com>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: Re: linux-next: build warning after merge of the ftrace tree
Date: Thu, 14 Nov 2019 22:43:24 -0500 [thread overview]
Message-ID: <20191114224324.108486d8@oasis.local.home> (raw)
In-Reply-To: <20191115140213.74c5efe7@canb.auug.org.au>
On Fri, 15 Nov 2019 14:02:13 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> In file included from kernel/trace/trace.c:52:
> kernel/trace/trace.h:804:13: warning: 'latency_fsnotify' defined but not used [-Wunused-function]
> 804 | static void latency_fsnotify(struct trace_array *tr) { }
> | ^~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> 91edde2e6ae1 ("ftrace: Implement fs notification for tracing_max_latency")
>
> "inline" missing :-(
>
Thanks for pointing that out, I'll go and fix this.
-- Steve
next prev parent reply other threads:[~2019-11-15 3:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 3:02 linux-next: build warning after merge of the ftrace tree Stephen Rothwell
2019-11-15 3:43 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-23 4:35 Stephen Rothwell
2023-06-23 6:53 ` Donglin Peng
2022-11-25 3:10 Stephen Rothwell
2021-10-28 12:23 Stephen Rothwell
2021-10-28 13:16 ` Steven Rostedt
2021-10-28 21:10 ` Stephen Rothwell
2021-10-28 21:29 ` Kalesh Singh
2021-10-28 22:36 ` Stephen Rothwell
2021-10-28 21:30 ` Steven Rostedt
2021-10-25 23:35 Stephen Rothwell
2021-10-26 12:15 ` Masami Hiramatsu
2021-10-25 4:39 Stephen Rothwell
2021-10-25 6:13 ` Masami Hiramatsu
2021-08-23 9:58 Stephen Rothwell
2021-08-23 14:00 ` Steven Rostedt
2021-08-24 10:53 ` Stephen Rothwell
2020-11-16 6:35 Stephen Rothwell
2020-11-16 17:43 ` Steven Rostedt
2020-11-16 19:24 ` Jonathan Corbet
2020-11-16 20:25 ` Steven Rostedt
2020-11-16 20:29 ` Jonathan Corbet
2020-11-16 20:35 ` Steven Rostedt
2020-08-05 4:21 Stephen Rothwell
2014-06-04 6:09 Stephen Rothwell
2014-06-04 16:26 ` Steven Rostedt
2014-06-04 16:49 ` Stephen Rothwell
2014-06-05 0:20 ` Fengguang Wu
2014-06-05 1:00 ` Steven Rostedt
2014-06-05 1:03 ` Fengguang Wu
2014-06-05 1:12 ` Steven Rostedt
2014-06-05 1:20 ` Steven Rostedt
2014-06-05 1:33 ` Fengguang Wu
2014-06-05 1:39 ` Steven Rostedt
2014-06-05 2:14 ` Fengguang Wu
2014-06-05 2:36 ` Steven Rostedt
2014-06-05 2:50 ` Fengguang Wu
2014-06-05 3:03 ` Fengguang Wu
2014-06-05 3:13 ` Steven Rostedt
2014-06-05 3:42 ` Fengguang Wu
2014-06-05 2:38 ` Steven Rostedt
2014-06-05 2:44 ` Fengguang Wu
2014-06-05 2:46 ` Steven Rostedt
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=20191114224324.108486d8@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viktor.rosendahl@gmail.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).