From: kernel test robot <lkp@intel.com>
To: Tyrel Datwyler <tyreld@linux.ibm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-renesas-soc@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: [geert-renesas-drivers:master 4646/4880] Warning: drivers/scsi/ibmvscsi/ibmvfc-core.c:4942 function parameter 'protocol' not described in 'ibmvfc_alloc_target'
Date: Thu, 16 Jul 2026 05:40:28 +0800 [thread overview]
Message-ID: <202607160546.9qT6UbFy-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git master
head: cbf4a77e77ce7c4a2907a798c7f624dfaf65da57
commit: 275460787107280d4e1f7946d6d17ea070780cef [4646/4880] scsi: ibmvfc: Allocate targets based on protocol
config: powerpc64-randconfig-002-20260715 (https://download.01.org/0day-ci/archive/20260716/202607160546.9qT6UbFy-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project b3e6e6dabdc02153552a64fc74ff5c7532447eed)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260716/202607160546.9qT6UbFy-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/202607160546.9qT6UbFy-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/scsi/ibmvscsi/ibmvfc-core.c:4942 function parameter 'protocol' not described in 'ibmvfc_alloc_target'
>> Warning: drivers/scsi/ibmvscsi/ibmvfc-core.c:4942 function parameter 'protocol' not described in 'ibmvfc_alloc_target'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-15 21:40 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=202607160546.9qT6UbFy-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tyreld@linux.ibm.com \
/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