[<prev] [next>] [day] [month] [year] [list]
Message-ID: <202311212050.Z3EDRIR3-lkp@intel.com>
Date: Tue, 21 Nov 2023 20:18:20 +0800
From: kernel test robot <lkp@...el.com>
To: Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>,
ryder.lee@...iatek.com, jianjun.wang@...iatek.com,
lpieralisi@...nel.org, kw@...ux.com, robh@...nel.org,
bhelgaas@...gle.com, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com, linux-pci@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Cc: oe-kbuild-all@...ts.linux.dev
Subject: Re: [PATCH v2] PCI: mediatek: Fix sparse warning caused to
virt_to_phys() prototype change
Hi Stanislav,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/next]
[also build test WARNING on pci/for-linus linus/master v6.7-rc2 next-20231121]
[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/Stanislav-Kinsburskii/PCI-mediatek-Fix-sparse-warning-caused-to-virt_to_phys-prototype-change/20231121-080253
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/170052491316.21557.13173111699965824301.stgit%40skinsburskii.
patch subject: [PATCH v2] PCI: mediatek: Fix sparse warning caused to virt_to_phys() prototype change
config: s390-randconfig-r113-20231121 (https://download.01.org/0day-ci/archive/20231121/202311212050.Z3EDRIR3-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231121/202311212050.Z3EDRIR3-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311212050.Z3EDRIR3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pci/controller/pcie-mediatek.c:400:62: sparse: sparse: incorrect type in argument 1 (different modifiers) @@ expected void volatile *address @@ got void const * @@
drivers/pci/controller/pcie-mediatek.c:400:62: sparse: expected void volatile *address
drivers/pci/controller/pcie-mediatek.c:400:62: sparse: got void const *
drivers/pci/controller/pcie-mediatek.c:523:66: sparse: sparse: incorrect type in argument 1 (different modifiers) @@ expected void volatile *address @@ got void const * @@
drivers/pci/controller/pcie-mediatek.c:523:66: sparse: expected void volatile *address
drivers/pci/controller/pcie-mediatek.c:523:66: sparse: got void const *
vim +400 drivers/pci/controller/pcie-mediatek.c
393
394 static void mtk_compose_msi_msg(struct irq_data *data, struct msi_msg *msg)
395 {
396 struct mtk_pcie_port *port = irq_data_get_irq_chip_data(data);
397 phys_addr_t addr;
398
399 /* MT2712/MT7622 only support 32-bit MSI addresses */
> 400 addr = virt_to_phys((__force const void *)port->base + PCIE_MSI_VECTOR);
401 msg->address_hi = 0;
402 msg->address_lo = lower_32_bits(addr);
403
404 msg->data = data->hwirq;
405
406 dev_dbg(port->pcie->dev, "msi#%d address_hi %#x address_lo %#x\n",
407 (int)data->hwirq, msg->address_hi, msg->address_lo);
408 }
409
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists