From: kernel test robot <lkp@intel.com>
To: superm1@kernel.org, Bjorn Helgaas <helgaas@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
"open list : PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
"open list : USB XHCI DRIVER" <linux-usb@vger.kernel.org>,
"Daniel Drake" <drake@endlessos.org>, "Gary Li" <Gary.Li@amd.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v3 1/5] PCI: Use an enum for reset type in pci_dev_wait()
Date: Sat, 13 Jul 2024 16:38:13 +0800 [thread overview]
Message-ID: <202407131650.S68TetNP-lkp@intel.com> (raw)
In-Reply-To: <20240712181246.811044-2-superm1@kernel.org>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on usb/usb-next usb/usb-linus westeri-thunderbolt/next linus/master v6.10-rc7 next-20240712]
[cannot apply to pci/next pci/for-linus]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/superm1-kernel-org/PCI-Use-an-enum-for-reset-type-in-pci_dev_wait/20240713-022018
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
patch link: https://lore.kernel.org/r/20240712181246.811044-2-superm1%40kernel.org
patch subject: [PATCH v3 1/5] PCI: Use an enum for reset type in pci_dev_wait()
config: x86_64-randconfig-121-20240713 (https://download.01.org/0day-ci/archive/20240713/202407131650.S68TetNP-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240713/202407131650.S68TetNP-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/202407131650.S68TetNP-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pci/pci.c:184:12: sparse: sparse: symbol 'pci_reset_types' was not declared. Should it be static?
drivers/pci/pci.c:1208:36: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted pci_power_t [usertype] current_state @@ got int @@
drivers/pci/pci.c:1208:36: sparse: expected restricted pci_power_t [usertype] current_state
drivers/pci/pci.c:1208:36: sparse: got int
drivers/pci/pci.c:1367:15: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted pci_power_t [assigned] [usertype] state @@ got int @@
drivers/pci/pci.c:1367:15: sparse: expected restricted pci_power_t [assigned] [usertype] state
drivers/pci/pci.c:1367:15: sparse: got int
drivers/pci/pci.c:1369:50: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1369:69: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1422:28: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted pci_power_t [usertype] current_state @@ got int @@
drivers/pci/pci.c:1422:28: sparse: expected restricted pci_power_t [usertype] current_state
drivers/pci/pci.c:1422:28: sparse: got int
drivers/pci/pci.c:1512:16: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1512:35: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1512:52: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1512:70: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1534:15: sparse: sparse: invalid assignment: |=
drivers/pci/pci.c:1534:15: sparse: left side has type unsigned short
drivers/pci/pci.c:1534:15: sparse: right side has type restricted pci_power_t
drivers/pci/pci.c:1546:28: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted pci_power_t [usertype] current_state @@ got int @@
drivers/pci/pci.c:1546:28: sparse: expected restricted pci_power_t [usertype] current_state
drivers/pci/pci.c:1546:28: sparse: got int
drivers/pci/pci.c:1563:13: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1563:21: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1565:18: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1565:26: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1588:13: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1588:22: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1920:38: sparse: sparse: array of flexible structures
drivers/pci/pci.c:2370:44: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2689:60: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2690:30: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2861:20: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2861:38: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2884:49: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2884:67: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:4580:13: sparse: sparse: invalid assignment: |=
drivers/pci/pci.c:4580:13: sparse: left side has type unsigned short
drivers/pci/pci.c:4580:13: sparse: right side has type restricted pci_power_t
drivers/pci/pci.c:4585:13: sparse: sparse: invalid assignment: |=
drivers/pci/pci.c:4585:13: sparse: left side has type unsigned short
drivers/pci/pci.c:4585:13: sparse: right side has type restricted pci_power_t
drivers/pci/pci.c: note: in included file (through include/linux/resource_ext.h, include/linux/acpi.h):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
drivers/pci/pci.c:1163:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected int @@ got restricted pci_power_t [usertype] @@
drivers/pci/pci.c:1163:24: sparse: expected int
drivers/pci/pci.c:1163:24: sparse: got restricted pci_power_t [usertype]
drivers/pci/pci.c:1163:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected int @@ got restricted pci_power_t [usertype] @@
drivers/pci/pci.c:1163:24: sparse: expected int
drivers/pci/pci.c:1163:24: sparse: got restricted pci_power_t [usertype]
vim +/pci_reset_types +184 drivers/pci/pci.c
183
> 184 const char * const pci_reset_types[] = {
185 "FLR",
186 "AF_FLR",
187 "PM D3HOT->D0",
188 "bus reset",
189 "resume",
190 "DPC",
191 };
192
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-13 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 18:12 [PATCH v3 0/5] Verify devices transition from D3cold to D0 superm1
2024-07-12 18:12 ` [PATCH v3 1/5] PCI: Use an enum for reset type in pci_dev_wait() superm1
2024-07-13 8:38 ` kernel test robot [this message]
2024-07-15 12:36 ` Ilpo Järvinen
2024-07-12 18:12 ` [PATCH v3 2/5] PCI: Check PCI_PM_CTRL instead of PCI_COMMAND " superm1
2024-07-12 18:12 ` [PATCH v3 3/5] PCI: Verify functions currently in D3cold have entered D0 superm1
2024-07-12 18:12 ` [PATCH v3 4/5] PCI: Allow Ryzen XHCI controllers into D3cold and drop delays superm1
2024-07-12 18:12 ` [PATCH v3 5/5] PCI: Drop Radeon quirk for Macbook Pro 8.2 superm1
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=202407131650.S68TetNP-lkp@intel.com \
--to=lkp@intel.com \
--cc=Gary.Li@amd.com \
--cc=drake@endlessos.org \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mathias.nyman@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=superm1@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).