From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:bcachefs-garbage 209/258] include/linux/pipe_fs_i.h:274:29: warning: 'struct iov_iter' declared inside parameter list will not be visible outside of this definition or declaration
Date: Tue, 10 Sep 2024 03:27:44 +0800 [thread overview]
Message-ID: <202409100312.OM4xSTGF-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs bcachefs-garbage
head: c88c2220b6b527cec382f06a0ba3feab2a593b37
commit: 79e9f469b262e253396d71d7af0945da30a61cd0 [209/258] bcachefs: convert thread_with_stdio to pipes WIP
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240910/202409100312.OM4xSTGF-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240910/202409100312.OM4xSTGF-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/202409100312.OM4xSTGF-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/splice.h:12,
from net/tls/tls_sw.c:42:
>> include/linux/pipe_fs_i.h:274:29: warning: 'struct iov_iter' declared inside parameter list will not be visible outside of this definition or declaration
274 | struct iov_iter *to,
| ^~~~~~~~
include/linux/pipe_fs_i.h:277:30: warning: 'struct iov_iter' declared inside parameter list will not be visible outside of this definition or declaration
277 | struct iov_iter *to,
| ^~~~~~~~
vim +274 include/linux/pipe_fs_i.h
272
273 ssize_t do_pipe_read(struct pipe_inode_info *pipe,
> 274 struct iov_iter *to,
275 bool nonblock);
276 ssize_t do_pipe_write(struct pipe_inode_info *pipe,
277 struct iov_iter *to,
278 bool nonblock,
279 bool is_packetized);
280
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-09 19:27 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=202409100312.OM4xSTGF-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@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.