From: kernel test robot <lkp@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] dma-buf: add no-op stubs when CONFIG_DMA_SHARED_BUFFER is disabled
Date: Thu, 27 Nov 2025 17:24:19 +0800 [thread overview]
Message-ID: <202511271739.cjidjUdn-lkp@intel.com> (raw)
In-Reply-To: <6202945f4af2d10e0fb6602b25ff9cb454c1ee85.1764229204.git.viresh.kumar@linaro.org>
Hi Viresh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on sailus-media-tree/master]
[also build test WARNING on linus/master v6.18-rc7 next-20251127]
[cannot apply to sailus-media-tree/streams]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Viresh-Kumar/dma-buf-add-no-op-stubs-when-CONFIG_DMA_SHARED_BUFFER-is-disabled/20251127-154307
base: git://linuxtv.org/sailus/media_tree.git master
patch link: https://lore.kernel.org/r/6202945f4af2d10e0fb6602b25ff9cb454c1ee85.1764229204.git.viresh.kumar%40linaro.org
patch subject: [PATCH] dma-buf: add no-op stubs when CONFIG_DMA_SHARED_BUFFER is disabled
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20251127/202511271739.cjidjUdn-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251127/202511271739.cjidjUdn-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/202511271739.cjidjUdn-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from io_uring/io_uring.c:101:
In file included from io_uring/zcrx.h:6:
>> include/linux/dma-buf.h:660:51: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
660 | dma_buf_map_attachment(struct dma_buf_attachment *, enum dma_data_direction)
| ^
include/linux/dma-buf.h:660:76: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
660 | dma_buf_map_attachment(struct dma_buf_attachment *, enum dma_data_direction)
| ^
include/linux/dma-buf.h:665:72: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
665 | static inline void dma_buf_unmap_attachment(struct dma_buf_attachment *,
| ^
include/linux/dma-buf.h:666:27: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
666 | struct sg_table *,
| ^
include/linux/dma-buf.h:667:33: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
667 | enum dma_data_direction) { }
| ^
include/linux/dma-buf.h:695:48: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
695 | static inline int dma_buf_mmap(struct dma_buf *, struct vm_area_struct *,
| ^
include/linux/dma-buf.h:695:73: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
695 | static inline int dma_buf_mmap(struct dma_buf *, struct vm_area_struct *,
| ^
include/linux/dma-buf.h:696:24: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
696 | unsigned long)
| ^
8 warnings generated.
vim +660 include/linux/dma-buf.h
658
659 static inline struct sg_table *
> 660 dma_buf_map_attachment(struct dma_buf_attachment *, enum dma_data_direction)
661 {
662 return NULL;
663 }
664
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-11-27 9:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6202945f4af2d10e0fb6602b25ff9cb454c1ee85.1764229204.git.viresh.kumar@linaro.org>]
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=202511271739.cjidjUdn-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox