From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [gourryinverse:scratch/gourry/managed_nodes/node_features_v6 36/44] Warning: kernel/dma/contiguous.c:248 Incorrect use of kernel-doc format: * dma_contiguous_owns_node - is a DMA-owned CMA area hosted by this node?
Date: Thu, 20 Aug 2026 11:54:37 +0200 [thread overview]
Message-ID: <202608201130.TBzEj1XV-lkp@intel.com> (raw)
tree: https://github.com/gourryinverse/linux scratch/gourry/managed_nodes/node_features_v6
head: 38c7f48162aa282dc6a9edfb7011378594057c10
commit: ee74567d3e72b82b307fe5704b4ceec6af0f44bc [36/44] dma-contiguous: add dma_contiguous_owns_node()
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260820/202608201130.TBzEj1XV-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260820/202608201130.TBzEj1XV-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/202608201130.TBzEj1XV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: kernel/dma/contiguous.c:248 Incorrect use of kernel-doc format: * dma_contiguous_owns_node - is a DMA-owned CMA area hosted by this node?
>> Warning: kernel/dma/contiguous.c:259 function parameter 'nid' not described in 'dma_contiguous_owns_node'
>> Warning: kernel/dma/contiguous.c:259 expecting prototype for dma_contiguous_reserve(). Prototype was for dma_contiguous_owns_node() instead
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-20 9:55 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=202608201130.TBzEj1XV-lkp@intel.com \
--to=lkp@intel.com \
--cc=gourry@gourry.net \
--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.