From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [anolis-intel-cloud:devel-6.6 218/218] tools/testing/selftests/vfio/lib/drivers/ioat/hw.h:67:35: warning: 'struct pci_dev' declared inside parameter list will not be visible outside of this definition or declaration
Date: Thu, 23 Apr 2026 00:02:38 +0200 [thread overview]
Message-ID: <202604230035.jb0qRkl2-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: aubrey.li@linux.intel.com
tree: https://gitee.com/anolis/intel-cloud-kernel.git devel-6.6
head: db8b81c14b7031c5b1420d57fbeb18056546ddcf
commit: c87d9db7252351cec95ecaa559f4cf1823eff6d3 [218/218] anolis: tools: selftests: Sync vfio tests with upstream
:::::: branch date: 10 hours ago
:::::: commit date: 14 hours ago
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260423/202604230035.jb0qRkl2-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/20260423/202604230035.jb0qRkl2-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/r/202604230035.jb0qRkl2-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from tools/testing/selftests/vfio/lib/drivers/ioat/ioat.c:14:
>> tools/testing/selftests/vfio/lib/drivers/ioat/hw.h:67:35: warning: 'struct pci_dev' declared inside parameter list will not be visible outside of this definition or declaration
67 | int system_has_dca_enabled(struct pci_dev *pdev);
| ^~~~~~~
vim +67 tools/testing/selftests/vfio/lib/drivers/ioat/hw.h
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-22 22:03 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=202604230035.jb0qRkl2-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 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.