From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [axboe-block:rw_iter 29/438] drivers/char/nwflash.c:129:40: error: use of undeclared identifier 'ppos'
Date: Sun, 14 Apr 2024 15:32:35 +0800 [thread overview]
Message-ID: <202404141542.cP2ElTE1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git rw_iter
head: 4855883f3d590ecdf8f8870966dad5ca923dd6ce
commit: 55a4bb61a27afcdd2e5258639821ad6f57bdd166 [29/438] char/nwflash: convert to read/write iterators
config: arm-footbridge_defconfig (https://download.01.org/0day-ci/archive/20240414/202404141542.cP2ElTE1-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 8b3b4a92adee40483c27f26c478a384cd69c6f05)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240414/202404141542.cP2ElTE1-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/202404141542.cP2ElTE1-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/char/nwflash.c:22:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:522:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
>> drivers/char/nwflash.c:129:40: error: use of undeclared identifier 'ppos'
129 | "buffer=%p, count=0x%zx.\n", *ppos, buf, size);
| ^
>> drivers/char/nwflash.c:129:46: error: use of undeclared identifier 'buf'
129 | "buffer=%p, count=0x%zx.\n", *ppos, buf, size);
| ^
>> drivers/char/nwflash.c:129:51: error: use of undeclared identifier 'size'
129 | "buffer=%p, count=0x%zx.\n", *ppos, buf, size);
| ^
1 warning and 3 errors generated.
vim +/ppos +129 drivers/char/nwflash.c
^1da177e4c3f415 Linus Torvalds 2005-04-16 122
55a4bb61a27afcd Jens Axboe 2024-04-09 123 static ssize_t flash_read(struct kiocb *iocb, struct iov_iter *to)
^1da177e4c3f415 Linus Torvalds 2005-04-16 124 {
6ee8928d94841aa Akinobu Mita 2008-07-25 125 ssize_t ret;
^1da177e4c3f415 Linus Torvalds 2005-04-16 126
^1da177e4c3f415 Linus Torvalds 2005-04-16 127 if (flashdebug)
4ef584ba84125b6 Russell King 2008-07-26 128 printk(KERN_DEBUG "flash_read: flash_read: offset=0x%llx, "
4ef584ba84125b6 Russell King 2008-07-26 @129 "buffer=%p, count=0x%zx.\n", *ppos, buf, size);
^1da177e4c3f415 Linus Torvalds 2005-04-16 130 /*
^1da177e4c3f415 Linus Torvalds 2005-04-16 131 * We now lock against reads and writes. --rmk
^1da177e4c3f415 Linus Torvalds 2005-04-16 132 */
6f87f0deebaff27 Ingo Molnar 2006-03-23 133 if (mutex_lock_interruptible(&nwflash_mutex))
^1da177e4c3f415 Linus Torvalds 2005-04-16 134 return -ERESTARTSYS;
^1da177e4c3f415 Linus Torvalds 2005-04-16 135
55a4bb61a27afcd Jens Axboe 2024-04-09 136 ret = simple_copy_to_iter((void *)FLASH_BASE, &iocb->ki_pos,
55a4bb61a27afcd Jens Axboe 2024-04-09 137 gbFlashSize, to);
6f87f0deebaff27 Ingo Molnar 2006-03-23 138 mutex_unlock(&nwflash_mutex);
6ee8928d94841aa Akinobu Mita 2008-07-25 139
^1da177e4c3f415 Linus Torvalds 2005-04-16 140 return ret;
^1da177e4c3f415 Linus Torvalds 2005-04-16 141 }
^1da177e4c3f415 Linus Torvalds 2005-04-16 142
:::::: The code at line 129 was first introduced by commit
:::::: 4ef584ba84125b67c17b5aded38e7783cd8cdef0 [ARM] fix nwflash.c: 6ee8928d94841aa764aeaf645ad16daff811dc26
:::::: TO: Russell King <rmk@dyn-67.arm.linux.org.uk>
:::::: CC: Russell King <rmk+kernel@arm.linux.org.uk>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-14 7:32 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=202404141542.cP2ElTE1-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--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