From: kernel test robot <lkp@intel.com>
To: daire.mcnamara@microchip.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v8 1/3] PCI: microchip: Fix outbound address translation tables
Date: Thu, 22 Aug 2024 15:54:05 +0800 [thread overview]
Message-ID: <202408221512.EL84YVBf-lkp@intel.com> (raw)
In-Reply-To: <20240821130217.957424-2-daire.mcnamara@microchip.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8400291e289ee6b2bf9779ff1c83a291501f017b]
url: https://github.com/intel-lab-lkp/linux/commits/daire-mcnamara-microchip-com/PCI-microchip-Fix-outbound-address-translation-tables/20240821-210421
base: 8400291e289ee6b2bf9779ff1c83a291501f017b
patch link: https://lore.kernel.org/r/20240821130217.957424-2-daire.mcnamara%40microchip.com
patch subject: [PATCH v8 1/3] PCI: microchip: Fix outbound address translation tables
config: openrisc-randconfig-r133-20240822 (https://download.01.org/0day-ci/archive/20240822/202408221512.EL84YVBf-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240822/202408221512.EL84YVBf-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/202408221512.EL84YVBf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pci/controller/plda/pcie-microchip-host.c:617:5: sparse: sparse: symbol 'mc_pcie_setup_iomems' was not declared. Should it be static?
vim +/mc_pcie_setup_iomems +617 drivers/pci/controller/plda/pcie-microchip-host.c
616
> 617 int mc_pcie_setup_iomems(struct pci_host_bridge *bridge,
618 struct plda_pcie_rp *port)
619 {
620 void __iomem *bridge_base_addr = port->bridge_addr;
621 struct resource_entry *entry;
622 u64 pci_addr;
623 u32 index = 1;
624
625 resource_list_for_each_entry(entry, &bridge->windows) {
626 if (resource_type(entry->res) == IORESOURCE_MEM) {
627 pci_addr = entry->res->start - entry->offset;
628 plda_pcie_setup_window(bridge_base_addr, index,
629 entry->res->start & MC_OUTBOUND_TRANS_TBL_MASK,
630 pci_addr, resource_size(entry->res));
631 index++;
632 }
633 }
634
635 return 0;
636 }
637
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-22 7:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 13:02 [PATCH v8 0/3] Fix address translations on MPFS PCIe controller daire.mcnamara
2024-08-21 13:02 ` daire.mcnamara
2024-08-21 13:02 ` [PATCH v8 1/3] PCI: microchip: Fix outbound address translation tables daire.mcnamara
2024-08-21 13:02 ` daire.mcnamara
2024-08-21 17:03 ` Bjorn Helgaas
2024-08-21 17:03 ` Bjorn Helgaas
2024-08-21 17:52 ` Ilpo Järvinen
2024-08-21 17:52 ` Ilpo Järvinen
2024-08-22 6:41 ` kernel test robot
2024-08-22 6:51 ` kernel test robot
2024-08-22 7:54 ` kernel test robot [this message]
2024-08-21 13:02 ` [PATCH v8 2/3] PCI: microchip: Fix inbound " daire.mcnamara
2024-08-21 13:02 ` daire.mcnamara
2024-08-21 17:17 ` Bjorn Helgaas
2024-08-21 17:17 ` Bjorn Helgaas
2024-08-21 13:02 ` [PATCH v8 3/3] dt-bindings: PCI: microchip,pcie-host: allow dma-noncoherent daire.mcnamara
2024-08-21 13:02 ` daire.mcnamara
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=202408221512.EL84YVBf-lkp@intel.com \
--to=lkp@intel.com \
--cc=daire.mcnamara@microchip.com \
--cc=oe-kbuild-all@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.