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] drivers/dma-buf/dma-buf.c:363: warning: Function parameter or member 'name' not described in 'dma_buf_set_name'
Date: Sat, 24 Oct 2026 20:54:47 +0800 [thread overview]
Message-ID: <202610242048.rON5p0DA-lkp@intel.com> (raw)
Hi Guangming,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android15-6.6
head: 60cf931c5a95dacbbd86483d5d0978e80a756ccd
commit: 05811b07b50aa107b805735f20c9029b40e9a7d9 [1/1] ANDROID: dma-buf: support users to change dma_buf.name
config: arm-randconfig-1001-20261020 (https://download.01.org/0day-ci/archive/20261024/202610242048.rON5p0DA-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/20261024/202610242048.rON5p0DA-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/202610242048.rON5p0DA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/dma-buf/dma-buf.c:363: warning: Function parameter or member 'name' not described in 'dma_buf_set_name'
drivers/dma-buf/dma-buf.c:363: warning: Excess function parameter 'buf' description in 'dma_buf_set_name'
vim +363 drivers/dma-buf/dma-buf.c
348
349 /**
350 * dma_buf_set_name - Set a name to a specific dma_buf to track the usage.
351 * It could support changing the name of the dma-buf if the same
352 * piece of memory is used for multiple purpose between different devices.
353 *
354 * @dmabuf: [in] dmabuf buffer that will be renamed.
355 * @buf: [in] A piece of userspace memory that contains the name of
356 * the dma-buf.
357 *
358 * Returns 0 on success. If the dma-buf buffer is already attached to
359 * devices, return -EBUSY.
360 *
361 */
362 long dma_buf_set_name(struct dma_buf *dmabuf, const char *name)
> 363 {
364 char *buf = kstrndup(name, DMA_BUF_NAME_LEN, GFP_KERNEL);
365 if (!buf)
366 return -ENOMEM;
367
368 _dma_buf_set_name(dmabuf, buf);
369
370 return 0;
371 }
372 EXPORT_SYMBOL_GPL(dma_buf_set_name);
373
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-10-24 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 12:54 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-25 5:12 [android-common:android15-6.6 1/1] drivers/dma-buf/dma-buf.c:363: warning: Function parameter or member 'name' not described in 'dma_buf_set_name' kernel test robot
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=202610242048.rON5p0DA-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.