From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] scripts/kernel-doc: Detect mismatched inline member documentation tags
Date: Sun, 19 Apr 2026 19:28:43 +0200 [thread overview]
Message-ID: <202604191910.GczJmXNT-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: llvm@lists.linux.dev
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260415215032.3398330-1-shuicheng.lin@intel.com>
References: <20260415215032.3398330-1-shuicheng.lin@intel.com>
TO: Shuicheng Lin <shuicheng.lin@intel.com>
TO: linux-kernel@vger.kernel.org
TO: intel-xe@lists.freedesktop.org
CC: Shuicheng Lin <shuicheng.lin@intel.com>
Hi Shuicheng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lwn/docs-next]
[also build test WARNING on linus/master v7.0 next-20260417]
[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/Shuicheng-Lin/scripts-kernel-doc-Detect-mismatched-inline-member-documentation-tags/20260419-144228
base: git://git.lwn.net/linux.git docs-next
patch link: https://lore.kernel.org/r/20260415215032.3398330-1-shuicheng.lin%40intel.com
patch subject: [PATCH] scripts/kernel-doc: Detect mismatched inline member documentation tags
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260419/202604191910.GczJmXNT-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/20260419/202604191910.GczJmXNT-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/r/202604191910.GczJmXNT-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: block/blk-map.c:366 Excess function parameter 'op' description in 'bio_copy_kern'
>> Warning: block/blk-map.c:366 Excess function parameter 'op' description in 'bio_copy_kern'
--
>> Warning: block/blk-mq-dma.c:379 Excess function parameter 'state' description in 'blk_rq_integrity_dma_map_iter_next'
>> Warning: block/blk-mq-dma.c:379 Excess function parameter 'state' description in 'blk_rq_integrity_dma_map_iter_next'
--
>> Warning: fs/inode.c:1306 Excess function parameter 'isnew' description in 'inode_insert5'
>> Warning: fs/inode.c:1306 Excess function parameter 'isnew' description in 'inode_insert5'
--
>> Warning: mm/swap_state.c:179 Excess function parameter 'gfp' description in 'swap_cache_add_folio'
>> Warning: mm/swap_state.c:179 Excess function parameter 'gfp' description in 'swap_cache_add_folio'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-04-19 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 17:28 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-20 1:44 [PATCH] scripts/kernel-doc: Detect mismatched inline member documentation tags kernel test robot
2026-04-20 1:44 kernel test robot
2026-04-15 21:50 Shuicheng Lin
2026-04-28 8:12 ` Jani Nikula
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=202604191910.GczJmXNT-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.