From: kernel test robot <lkp@intel.com>
To: Amey Narkhede <ameynarkhede03@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
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>,
Amey Narkhede <ameynarkhede03@gmail.com>
Subject: Re: [PATCH v6 8/8] PCI: Change the type of probe argument in reset functions
Date: Tue, 8 Jun 2021 06:58:26 +0800 [thread overview]
Message-ID: <202106080609.6Ohy34Eh-lkp@intel.com> (raw)
In-Reply-To: <20210607182137.5794-9-ameynarkhede03@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3397 bytes --]
Hi Amey,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on next-20210607]
[cannot apply to pm/linux-next cryptodev/master crypto/master linus/master v5.13-rc5]
[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/Expose-and-manage-PCI-device-reset/20210608-022554
base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
config: arm64-randconfig-r031-20210607 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project ae973380c5f6be77ce395022be40350942260be9)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://github.com/0day-ci/linux/commit/827552fbc3a1722cd8f6d5e81c4806670fd5545f
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Amey-Narkhede/Expose-and-manage-PCI-device-reset/20210608-022554
git checkout 827552fbc3a1722cd8f6d5e81c4806670fd5545f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/pci/pci.c:5139:4: error: incompatible function pointer types initializing 'int (*)(struct pci_dev *, pci_reset_mode_t)' (aka 'int (*)(struct pci_dev *, enum pci_reset_mode)') with an expression of type 'int (*)(struct pci_dev *, int)' [-Werror,-Wincompatible-function-pointer-types]
{ &pci_dev_acpi_reset, .name = "acpi" },
^~~~~~~~~~~~~~~~~~~
1 error generated.
vim +5139 drivers/pci/pci.c
3ebe7f9f7e4a4f Keith Busch 2014-05-02 5132
c09bbd373f3e96 Amey Narkhede 2021-06-07 5133 /*
c09bbd373f3e96 Amey Narkhede 2021-06-07 5134 * The ordering for functions in pci_reset_fn_methods is required for
c09bbd373f3e96 Amey Narkhede 2021-06-07 5135 * reset_methods byte array defined in struct pci_dev.
c09bbd373f3e96 Amey Narkhede 2021-06-07 5136 */
c09bbd373f3e96 Amey Narkhede 2021-06-07 5137 const struct pci_reset_fn_method pci_reset_fn_methods[] = {
c09bbd373f3e96 Amey Narkhede 2021-06-07 5138 { &pci_dev_specific_reset, .name = "device_specific" },
ccbe2295e8be73 Shanker Donthineni 2021-06-07 @5139 { &pci_dev_acpi_reset, .name = "acpi" },
c09bbd373f3e96 Amey Narkhede 2021-06-07 5140 { &pcie_reset_flr, .name = "flr" },
c09bbd373f3e96 Amey Narkhede 2021-06-07 5141 { &pci_af_flr, .name = "af_flr" },
c09bbd373f3e96 Amey Narkhede 2021-06-07 5142 { &pci_pm_reset, .name = "pm" },
c09bbd373f3e96 Amey Narkhede 2021-06-07 5143 { &pci_reset_bus_function, .name = "bus" },
c09bbd373f3e96 Amey Narkhede 2021-06-07 5144 };
c09bbd373f3e96 Amey Narkhede 2021-06-07 5145
---
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: 36844 bytes --]
next prev parent reply other threads:[~2021-06-07 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 18:21 [PATCH v6 0/8] Expose and manage PCI device reset Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 1/8] PCI: Add pcie_reset_flr to follow calling convention of other reset methods Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 2/8] PCI: Add new array for keeping track of ordering of " Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 3/8] PCI: Remove reset_fn field from pci_dev Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 4/8] PCI/sysfs: Allow userspace to query and set device reset mechanism Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 5/8] PCI: Setup ACPI_COMPANION early Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 6/8] PCI: Add support for ACPI _RST reset method Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 7/8] PCI: Enable NO_BUS_RESET quirk for Nvidia GPUs Amey Narkhede
2021-06-07 18:21 ` [PATCH v6 8/8] PCI: Change the type of probe argument in reset functions Amey Narkhede
2021-06-07 22:58 ` kernel test robot [this message]
2021-06-08 0:44 ` Shanker R Donthineni
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=202106080609.6Ohy34Eh-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.williamson@redhat.com \
--cc=ameynarkhede03@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=helgaas@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@kernel.org \
--cc=raphael.norwitz@nutanix.com \
--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