From: kernel test robot <lkp@intel.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: Warning: drivers/net/ethernet/intel/i40e/i40e_main.c:14261 function parameter 'lock_acquired' not described in 'i40e_vsi_reinit_setup'
Date: Wed, 01 Jul 2026 20:21:55 +0200 [thread overview]
Message-ID: <202607012033.6QDAWbzs-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Maciej-Fijalkowski/i40e-unregister-netdev-before-clearing-VSI-on-reinit-failure/20260701-204739
head: cfa21b49060a99436d8fce660a5dd43e93493011
commit: fcdb1a0b20aeead066836ecdfcb14e228348173a i40e: avoid deadlock when calling unregister_netdev()
date: 5 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260701/202607012033.6QDAWbzs-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260701/202607012033.6QDAWbzs-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/202607012033.6QDAWbzs-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/net/ethernet/intel/i40e/i40e_main.c:14261 function parameter 'lock_acquired' not described in 'i40e_vsi_reinit_setup'
>> Warning: drivers/net/ethernet/intel/i40e/i40e_main.c:14261 function parameter 'lock_acquired' not described in 'i40e_vsi_reinit_setup'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-01 18:22 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=202607012033.6QDAWbzs-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=maciej.fijalkowski@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox