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 9/12] fs/tracefs/inode.c:56:9: error: implicit declaration of function 'iov_iter_count' is invalid in C99
Date: Thu, 4 Apr 2024 07:29:26 +0800 [thread overview]
Message-ID: <202404040725.9Abdcjc9-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git rw_iter
head: 8e8fd62fac9e105d05cfda66070e98a3a255e1a0
commit: bb285b16cf180b4178bb9a45a8ffbf1ca5d9a701 [9/12] fs: convert remaining users of ->read and ->write to iterator variants
config: arm-defconfig (https://download.01.org/0day-ci/archive/20240404/202404040725.9Abdcjc9-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240404/202404040725.9Abdcjc9-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/202404040725.9Abdcjc9-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/tracefs/inode.c:56:9: error: implicit declaration of function 'iov_iter_count' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
return iov_iter_count(from);
^
1 error generated.
vim +/iov_iter_count +56 fs/tracefs/inode.c
53
54 static ssize_t default_write_file_iter(struct kiocb *iocb, struct iov_iter *from)
55 {
> 56 return iov_iter_count(from);
57 }
58
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-03 23:30 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=202404040725.9Abdcjc9-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 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.