From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 1/1] kernel/bpf/dmabuf_iter.c:128:29: warning: no previous prototype for 'bpf_iter_dmabuf_next'
Date: Sun, 21 Dec 2025 10:49:15 +0100 [thread overview]
Message-ID: <202512211046.chAx6DtB-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android15-6.6
head: 16aa689262af24cd0897f463b3d0dd9ecee6b37c
commit: 755db8b11c512ff80570c0a57821350f2ba67937 [1/1] BACKPORT: bpf: Add open coded dmabuf iterator
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20251221/202512211046.chAx6DtB-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251221/202512211046.chAx6DtB-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/202512211046.chAx6DtB-lkp@intel.com/
All warnings (new ones prefixed by >>):
kernel/bpf/dmabuf_iter.c:117:17: warning: no previous prototype for 'bpf_iter_dmabuf_new' [-Wmissing-prototypes]
117 | __bpf_kfunc int bpf_iter_dmabuf_new(struct bpf_iter_dmabuf *it)
| ^~~~~~~~~~~~~~~~~~~
>> kernel/bpf/dmabuf_iter.c:128:29: warning: no previous prototype for 'bpf_iter_dmabuf_next' [-Wmissing-prototypes]
128 | __bpf_kfunc struct dma_buf *bpf_iter_dmabuf_next(struct bpf_iter_dmabuf *it)
| ^~~~~~~~~~~~~~~~~~~~
>> kernel/bpf/dmabuf_iter.c:140:18: warning: no previous prototype for 'bpf_iter_dmabuf_destroy' [-Wmissing-prototypes]
140 | __bpf_kfunc void bpf_iter_dmabuf_destroy(struct bpf_iter_dmabuf *it)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/bpf_iter_dmabuf_next +128 kernel/bpf/dmabuf_iter.c
127
> 128 __bpf_kfunc struct dma_buf *bpf_iter_dmabuf_next(struct bpf_iter_dmabuf *it)
129 {
130 struct bpf_iter_dmabuf_kern *kit = (void *)it;
131
132 if (kit->dmabuf)
133 kit->dmabuf = dma_buf_iter_next(kit->dmabuf);
134 else
135 kit->dmabuf = dma_buf_iter_begin();
136
137 return kit->dmabuf;
138 }
139
> 140 __bpf_kfunc void bpf_iter_dmabuf_destroy(struct bpf_iter_dmabuf *it)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-21 9:49 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=202512211046.chAx6DtB-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.