All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Terry Bowman <terry.bowman@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>,
	Dan Williams <djbw@kernel.org>
Subject: Warning: drivers/pci/pcie/aer_cxl_vh.c:172 function parameter 'wd' not described in 'for_each_cxl_proto_err'
Date: Sat, 18 Jul 2026 10:32:33 +0200	[thread overview]
Message-ID: <202607181054.0FLVfvSc-lkp@intel.com> (raw)

Hi Terry,

First bad commit (maybe != root cause):

tree:   https://github.com/intel-lab-lkp/linux/commits/Terry-Bowman/cxl-ras-Fix-cxl_rch_get_aer_severity-wrong-severity-register/20260718-063140
head:   b690e48c644301b364eded646b27e0df0cf0d1e2
commit: 1af36d74a23c78f1be7749cf8cc46b6fd6413c82 PCI/AER: Introduce AER-CXL protocol error kfifo
date:   10 hours ago
config: x86_64-rhel-9.4-bpf (https://download.01.org/0day-ci/archive/20260718/202607181054.0FLVfvSc-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260718/202607181054.0FLVfvSc-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/202607181054.0FLVfvSc-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: drivers/pci/pcie/aer_cxl_vh.c:172 function parameter 'wd' not described in 'for_each_cxl_proto_err'
>> Warning: drivers/pci/pcie/aer_cxl_vh.c:172 function parameter 'fn' not described in 'for_each_cxl_proto_err'
>> Warning: drivers/pci/pcie/aer_cxl_vh.c:172 function parameter 'wd' not described in 'for_each_cxl_proto_err'
>> Warning: drivers/pci/pcie/aer_cxl_vh.c:172 function parameter 'fn' not described in 'for_each_cxl_proto_err'

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-18  8:33 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=202607181054.0FLVfvSc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=djbw@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=terry.bowman@amd.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 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.