From: kernel test robot <lkp@intel.com>
To: Anthony Krowiak <akrowiak@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: Warning: drivers/s390/crypto/vfio_ap_ops.c:312 function parameter 'q' not described in 'vfio_ap_wait_for_irqclear'
Date: Sun, 04 Oct 2026 15:55:41 +0200 [thread overview]
Message-ID: <202610041542.AGKuIjKy-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Anthony-Krowiak/s390-vfio-ap-Fix-leaks-of-pinned-NIB-and-registered-GISC/20260929-081832
head: 620a5e651a016fb89fe1738e2f63a1e8521ece1e
commit: 620a5e651a016fb89fe1738e2f63a1e8521ece1e s390/vfio-ap: replace guest-reachable WARNs with ratelimited warnings
date: 5 days ago
config: s390-randconfig-r2202-20261004 (https://download.01.org/0day-ci/archive/20261004/202610041542.AGKuIjKy-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 9.5.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261004/202610041542.AGKuIjKy-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/202610041542.AGKuIjKy-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/s390/crypto/vfio_ap_ops.c:312 function parameter 'q' not described in 'vfio_ap_wait_for_irqclear'
>> Warning: drivers/s390/crypto/vfio_ap_ops.c:312 Excess function parameter 'apqn' description in 'vfio_ap_wait_for_irqclear'
>> Warning: drivers/s390/crypto/vfio_ap_ops.c:312 function parameter 'q' not described in 'vfio_ap_wait_for_irqclear'
>> Warning: drivers/s390/crypto/vfio_ap_ops.c:312 Excess function parameter 'apqn' description in 'vfio_ap_wait_for_irqclear'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-04 13:56 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=202610041542.AGKuIjKy-lkp@intel.com \
--to=lkp@intel.com \
--cc=akrowiak@linux.ibm.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 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.