From: kernel test robot <lkp@intel.com>
To: "Steven Rostedt (Google)" <rostedt@goodmis.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 5016/10451] kernel/trace/trace.c:7534:37: error: 'last_boot_fops' defined but not used
Date: Fri, 5 Jul 2024 14:54:06 +0800 [thread overview]
Message-ID: <202407051402.LW9VtaLq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 0b58e108042b0ed28a71cd7edf5175999955b233
commit: 7a1d1e4b9639ff08b2f42605c2950ae1ba4a43bf [5016/10451] tracing/ring-buffer: Add last_boot_info file to boot instance
config: x86_64-sof-customedconfig-atom-defconfig (https://download.01.org/0day-ci/archive/20240705/202407051402.LW9VtaLq-lkp@intel.com/config)
compiler: gcc-11 (Ubuntu 11.4.0-4ubuntu1) 11.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240705/202407051402.LW9VtaLq-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407051402.LW9VtaLq-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/trace.c:7534:37: error: 'last_boot_fops' defined but not used [-Werror=unused-const-variable=]
7534 | static const struct file_operations last_boot_fops = {
| ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/last_boot_fops +7534 kernel/trace/trace.c
7533
> 7534 static const struct file_operations last_boot_fops = {
7535 .open = tracing_open_generic_tr,
7536 .read = tracing_last_boot_read,
7537 .llseek = generic_file_llseek,
7538 .release = tracing_release_generic_tr,
7539 };
7540
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-05 6:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202407051402.LW9VtaLq-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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