From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:container 3/15] kernel/container.c:148:36: warning: unused variable 'container_proc_ops'
Date: Sat, 24 May 2025 09:35:01 +0800 [thread overview]
Message-ID: <202505240904.O3FLNxGy-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git container
head: e934156b00c64a64a048108513ab445a232c2120
commit: a04b5d08723a675c6e3d5ba710a1ad8266678ebc [3/15] containers: Provide /proc/containers
config: hexagon-randconfig-001-20250524 (https://download.01.org/0day-ci/archive/20250524/202505240904.O3FLNxGy-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250524/202505240904.O3FLNxGy-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/202505240904.O3FLNxGy-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/container.c:148:36: warning: unused variable 'container_proc_ops' [-Wunused-const-variable]
148 | static const struct seq_operations container_proc_ops = {
| ^~~~~~~~~~~~~~~~~~
1 warning generated.
vim +/container_proc_ops +148 kernel/container.c
147
> 148 static const struct seq_operations container_proc_ops = {
149 .start = container_proc_start,
150 .next = container_proc_next,
151 .stop = container_proc_stop,
152 .show = container_proc_show,
153 };
154
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-24 1:35 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=202505240904.O3FLNxGy-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox