From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: samples/kfifo/bytestream-example.c:145:30: warning: unused variable 'fifo_proc_ops'
Date: Fri, 20 Aug 2021 05:40:52 +0800 [thread overview]
Message-ID: <202108200542.bAFbbNTi-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: d6d09a6942050f21b065a134169002b4d6b701ef
commit: 97a32539b9568bb653683349e5a76d02ff3c3e2c proc: convert everything to "struct proc_ops"
date: 1 year, 7 months ago
config: x86_64-buildonly-randconfig-r001-20210819 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d2b574a4dea5b718e4386bf2e26af0126e5978ce)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97a32539b9568bb653683349e5a76d02ff3c3e2c
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 97a32539b9568bb653683349e5a76d02ff3c3e2c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> samples/kfifo/bytestream-example.c:145:30: warning: unused variable 'fifo_proc_ops' [-Wunused-const-variable]
static const struct proc_ops fifo_proc_ops = {
^
1 warning generated.
--
>> samples/kfifo/inttype-example.c:138:30: warning: unused variable 'fifo_proc_ops' [-Wunused-const-variable]
static const struct proc_ops fifo_proc_ops = {
^
1 warning generated.
--
>> samples/kfifo/record-example.c:152:30: warning: unused variable 'fifo_proc_ops' [-Wunused-const-variable]
static const struct proc_ops fifo_proc_ops = {
^
1 warning generated.
vim +/fifo_proc_ops +145 samples/kfifo/bytestream-example.c
144
> 145 static const struct proc_ops fifo_proc_ops = {
146 .proc_read = fifo_read,
147 .proc_write = fifo_write,
148 .proc_lseek = noop_llseek,
149 };
150
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30257 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: samples/kfifo/bytestream-example.c:145:30: warning: unused variable 'fifo_proc_ops'
Date: Fri, 20 Aug 2021 05:40:52 +0800 [thread overview]
Message-ID: <202108200542.bAFbbNTi-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: d6d09a6942050f21b065a134169002b4d6b701ef
commit: 97a32539b9568bb653683349e5a76d02ff3c3e2c proc: convert everything to "struct proc_ops"
date: 1 year, 7 months ago
config: x86_64-buildonly-randconfig-r001-20210819 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d2b574a4dea5b718e4386bf2e26af0126e5978ce)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97a32539b9568bb653683349e5a76d02ff3c3e2c
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 97a32539b9568bb653683349e5a76d02ff3c3e2c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> samples/kfifo/bytestream-example.c:145:30: warning: unused variable 'fifo_proc_ops' [-Wunused-const-variable]
static const struct proc_ops fifo_proc_ops = {
^
1 warning generated.
--
>> samples/kfifo/inttype-example.c:138:30: warning: unused variable 'fifo_proc_ops' [-Wunused-const-variable]
static const struct proc_ops fifo_proc_ops = {
^
1 warning generated.
--
>> samples/kfifo/record-example.c:152:30: warning: unused variable 'fifo_proc_ops' [-Wunused-const-variable]
static const struct proc_ops fifo_proc_ops = {
^
1 warning generated.
vim +/fifo_proc_ops +145 samples/kfifo/bytestream-example.c
144
> 145 static const struct proc_ops fifo_proc_ops = {
146 .proc_read = fifo_read,
147 .proc_write = fifo_write,
148 .proc_lseek = noop_llseek,
149 };
150
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30257 bytes --]
next reply other threads:[~2021-08-19 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 21:40 kernel test robot [this message]
2021-08-19 21:40 ` samples/kfifo/bytestream-example.c:145:30: warning: unused variable 'fifo_proc_ops' kernel test robot
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=202108200542.bAFbbNTi-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.