From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Warning: drivers/usb/gadget/udc/bcm63xx_udc.c:1845 Excess function parameter 'driver' description in 'bcm63xx_udc_stop'
Date: Tue, 04 Aug 2026 14:38:57 +0800 [thread overview]
Message-ID: <202608041430.DbVPV31N-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Shuicheng Lin <shuicheng.lin@intel.com>
CC: Jonathan Corbet <corbet@lwn.net>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 848acc8ffe1b7cd5f1bf427b93069becfebc2c9d
commit: 46d9c16115cf046ce564f0230126cae785f73826 scripts/kernel-doc: Detect mismatched inline member documentation tags
date: 3 months ago
:::::: branch date: 11 hours ago
:::::: commit date: 3 months ago
config: mips-randconfig-r064-20260804 (https://download.01.org/0day-ci/archive/20260804/202608041430.DbVPV31N-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project bacfe2950f8218268fcc0a8765644ea0c15f0360)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260804/202608041430.DbVPV31N-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
| Fixes: 46d9c16115cf ("scripts/kernel-doc: Detect mismatched inline member documentation tags")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202608041430.DbVPV31N-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/usb/gadget/udc/bcm63xx_udc.c:1845 Excess function parameter 'driver' description in 'bcm63xx_udc_stop'
>> Warning: drivers/usb/gadget/udc/bcm63xx_udc.c:1845 Excess function parameter 'driver' description in 'bcm63xx_udc_stop'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-04 6:39 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=202608041430.DbVPV31N-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox