From: kernel test robot <lkp@intel.com>
To: Amey Narkhede <ameynarkhede03@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: kbuild-all@lists.01.org, alex.williamson@redhat.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kw@linux.com, Shanker Donthineni <sdonthineni@nvidia.com>,
Sinan Kaya <okaya@kernel.org>, Len Brown <lenb@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH v13 2/9] PCI: Add pcie_reset_flr to follow calling convention of other reset methods
Date: Mon, 2 Aug 2021 01:04:58 +0800 [thread overview]
Message-ID: <202108020046.TOZPE6k2-lkp@intel.com> (raw)
In-Reply-To: <20210801142518.1224-3-ameynarkhede03@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5623 bytes --]
Hi Amey,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on pci/next]
[also build test WARNING on pm/linux-next cryptodev/master crypto/master linus/master v5.14-rc3 next-20210730]
[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]
url: https://github.com/0day-ci/linux/commits/Amey-Narkhede/PCI-Expose-and-manage-PCI-device-reset/20210801-222806
base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
config: i386-randconfig-s002-20210801 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/ce304ecb5f2709fa58ef6f16cf8e89ddbd7e42cd
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Amey-Narkhede/PCI-Expose-and-manage-PCI-device-reset/20210801-222806
git checkout ce304ecb5f2709fa58ef6f16cf8e89ddbd7e42cd
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/pci/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/pci/pci.c:1052:13: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1052:21: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1052:31: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1052:39: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1061:35: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1061:54: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1062:19: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1062:37: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1092:23: sparse: sparse: invalid assignment: |=
drivers/pci/pci.c:1092:23: sparse: left side has type unsigned short
drivers/pci/pci.c:1092:23: sparse: right side has type restricted pci_power_t
drivers/pci/pci.c:1097:57: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1119:28: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted pci_power_t [usertype] current_state @@ got int @@
drivers/pci/pci.c:1119:28: sparse: expected restricted pci_power_t [usertype] current_state
drivers/pci/pci.c:1119:28: sparse: got int
drivers/pci/pci.c:1168:36: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted pci_power_t [usertype] current_state @@ got int @@
drivers/pci/pci.c:1168:36: sparse: expected restricted pci_power_t [usertype] current_state
drivers/pci/pci.c:1168:36: sparse: got int
drivers/pci/pci.c:1340:13: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1340:21: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1342:18: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1342:26: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1365:13: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1365:22: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1372:46: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1372:54: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:1730:38: sparse: sparse: array of flexible structures
drivers/pci/pci.c:1917:36: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted pci_power_t [usertype] current_state @@ got int @@
drivers/pci/pci.c:1917:36: sparse: expected restricted pci_power_t [usertype] current_state
drivers/pci/pci.c:1917:36: sparse: got int
drivers/pci/pci.c:2313:44: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2614:61: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2615:45: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2804:20: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2804:38: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2827:49: sparse: sparse: restricted pci_power_t degrades to integer
drivers/pci/pci.c:2827:67: sparse: sparse: restricted pci_power_t degrades to integer
>> drivers/pci/pci.c:4636:6: sparse: sparse: symbol 'pcie_has_flr' was not declared. Should it be static?
drivers/pci/pci.c:4768:13: sparse: sparse: invalid assignment: |=
drivers/pci/pci.c:4768:13: sparse: left side has type unsigned short
drivers/pci/pci.c:4768:13: sparse: right side has type restricted pci_power_t
drivers/pci/pci.c:4773:13: sparse: sparse: invalid assignment: |=
drivers/pci/pci.c:4773:13: sparse: left side has type unsigned short
drivers/pci/pci.c:4773:13: sparse: right side has type restricted pci_power_t
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38524 bytes --]
next prev parent reply other threads:[~2021-08-01 17:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 14:25 [PATCH v13 0/9] PCI: Expose and manage PCI device reset Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 1/9] PCI: Cache PCIe FLR capability Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 2/9] PCI: Add pcie_reset_flr to follow calling convention of other reset methods Amey Narkhede
2021-08-01 17:04 ` kernel test robot [this message]
2021-08-01 17:05 ` [RFC PATCH] PCI: pcie_has_flr() can be static kernel test robot
2021-08-01 18:17 ` [PATCH v13 2/9] PCI: Add pcie_reset_flr to follow calling convention of other reset methods kernel test robot
2021-08-02 22:44 ` Bjorn Helgaas
2021-08-03 4:49 ` Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 3/9] PCI: Add new array for keeping track of ordering of " Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 4/9] PCI: Remove reset_fn field from pci_dev Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 5/9] PCI: Allow userspace to query and set device reset mechanism Amey Narkhede
2021-08-02 22:55 ` Bjorn Helgaas
2021-08-03 6:34 ` Amey Narkhede
2021-08-03 13:45 ` Shanker R Donthineni
2021-08-01 14:25 ` [PATCH v13 6/9] PCI: Define a function to set ACPI_COMPANION in pci_dev Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 7/9] PCI: Setup ACPI fwnode early and at the same time with OF Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 8/9] PCI: Add support for ACPI _RST reset method Amey Narkhede
2021-08-01 14:25 ` [PATCH v13 9/9] PCI: Change the type of probe argument in reset functions Amey Narkhede
2021-08-02 22:59 ` Bjorn Helgaas
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=202108020046.TOZPE6k2-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.williamson@redhat.com \
--cc=ameynarkhede03@gmail.com \
--cc=helgaas@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kw@linux.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@kernel.org \
--cc=raphael.norwitz@nutanix.com \
--cc=rjw@rjwysocki.net \
--cc=sdonthineni@nvidia.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 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).