From: Steven Rostedt <rostedt@goodmis.org>
To: kernel test robot <lkp@intel.com>
Cc: chongjiapeng <jiapeng.chong@linux.alibaba.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: Re: kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable'
Date: Mon, 14 Feb 2022 10:20:00 -0500 [thread overview]
Message-ID: <20220214102000.1d3af66e@gandalf.local.home> (raw)
In-Reply-To: <202202132037.4aN017dU-lkp@intel.com>
On Sun, 13 Feb 2022 21:03:29 +0800
kernel test robot <lkp@intel.com> wrote:
> All errors (new ones prefixed by >>):
>
> >> kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable' [-Werror,-Wunused-function]
> static inline void ftrace_startup_enable(int command) { }
> ^
> 1 error generated.
Strange. I always thought that static inline functions do not cause
warnings when not used? Especially, since they are often in headers when
things are turned off. Or is it because this is in a C file?
Is this a new warning caused by a commit, or is it a new warning because
the compiler now complains about it?
-- Steve
>
>
> vim +/ftrace_startup_enable +7157 kernel/trace/ftrace.c
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: kbuild-all@lists.01.org
Subject: Re: kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable'
Date: Mon, 14 Feb 2022 10:20:00 -0500 [thread overview]
Message-ID: <20220214102000.1d3af66e@gandalf.local.home> (raw)
In-Reply-To: <202202132037.4aN017dU-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
On Sun, 13 Feb 2022 21:03:29 +0800
kernel test robot <lkp@intel.com> wrote:
> All errors (new ones prefixed by >>):
>
> >> kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable' [-Werror,-Wunused-function]
> static inline void ftrace_startup_enable(int command) { }
> ^
> 1 error generated.
Strange. I always thought that static inline functions do not cause
warnings when not used? Especially, since they are often in headers when
things are turned off. Or is it because this is in a C file?
Is this a new warning caused by a commit, or is it a new warning because
the compiler now complains about it?
-- Steve
>
>
> vim +/ftrace_startup_enable +7157 kernel/trace/ftrace.c
next prev parent reply other threads:[~2022-02-14 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 13:03 kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable' kernel test robot
2022-02-13 13:03 ` kernel test robot
2022-02-14 15:20 ` Steven Rostedt [this message]
2022-02-14 15:20 ` Steven Rostedt
2022-02-14 15:53 ` Nathan Chancellor
2022-02-14 15:53 ` Nathan Chancellor
2022-02-14 16:28 ` Masahiro Yamada
2022-02-14 16:28 ` Masahiro Yamada
2022-02-14 17:00 ` Nathan Chancellor
2022-02-14 17:00 ` Nathan Chancellor
2022-02-14 18:57 ` Steven Rostedt
2022-02-14 18:57 ` 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=20220214102000.1d3af66e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.