From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> To: kbuild test robot <lkp@intel.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net> Cc: kbuild-all@01.org, linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>, Will Deacon <will.deacon@arm.com>, Robert Moore <robert.moore@intel.com>, Hanjun Guo <hanjun.guo@linaro.org>, Feng Kan <fkan@apm.com>, Jon Masters <jcm@redhat.com>, Zhang Rui <rui.zhang@intel.com>, Nate Watterson <nwatters@codeaurora.org> Subject: Re: [PATCH v3 3/5] ACPI: Introduce DMA ranges parsing Date: Sun, 6 Aug 2017 10:42:20 +0100 [thread overview] Message-ID: <20170806094219.GA16298@red-moon> (raw) In-Reply-To: <201708061311.4aEB8P1Q%fengguang.wu@intel.com> On Sun, Aug 06, 2017 at 01:12:55PM +0800, kbuild test robot wrote: > Hi Lorenzo, > > [auto build test ERROR on pm/linux-next] > [also build test ERROR on v4.13-rc3 next-20170804] > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] > > url: https://github.com/0day-ci/linux/commits/Lorenzo-Pieralisi/ACPICA-resource_mgr-Allow-_DMA-method-in-walk-resources/20170804-185152 > base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next > config: ia64-allnoconfig (attached as .config) > compiler: ia64-linux-gcc (GCC) 6.2.0 > reproduce: > wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # save the attached .config to linux build tree > make.cross ARCH=ia64 > > Note: the linux-review/Lorenzo-Pieralisi/ACPICA-resource_mgr-Allow-_DMA-method-in-walk-resources/20170804-185152 HEAD 37e91dddbbeb771d4df0001f716607f1dd8719f8 builds fine. > It only hurts bisectibility. Sigh, it is a silly v2->v3 rebase mistake, a change hunk that should be in patch 4 ended up in patch 3, series as a whole is fine but this must be fixed. Rafael, please let me know the best way to handle this, I think me sending a v4 is the simplest so that you can just update the branch. Apologies and thanks. Lorenzo > All errors (new ones prefixed by >>): > > drivers/acpi/scan.c: In function 'acpi_dma_configure': > >> drivers/acpi/scan.c:1451:2: error: implicit declaration of function 'iort_dma_setup' [-Werror=implicit-function-declaration] > iort_dma_setup(dev, &dma_addr, &size); > ^~~~~~~~~~~~~~ > cc1: some warnings being treated as errors > > vim +/iort_dma_setup +1451 drivers/acpi/scan.c > > 1440 > 1441 /** > 1442 * acpi_dma_configure - Set-up DMA configuration for the device. > 1443 * @dev: The pointer to the device > 1444 * @attr: device dma attributes > 1445 */ > 1446 int acpi_dma_configure(struct device *dev, enum dev_dma_attr attr) > 1447 { > 1448 const struct iommu_ops *iommu; > 1449 u64 dma_addr = 0, size = 0; > 1450 > > 1451 iort_dma_setup(dev, &dma_addr, &size); > 1452 > 1453 iommu = iort_iommu_configure(dev); > 1454 if (IS_ERR(iommu) && PTR_ERR(iommu) == -EPROBE_DEFER) > 1455 return -EPROBE_DEFER; > 1456 > 1457 arch_setup_dma_ops(dev, dma_addr, size, > 1458 iommu, attr == DEV_DMA_COHERENT); > 1459 > 1460 return 0; > 1461 } > 1462 EXPORT_SYMBOL_GPL(acpi_dma_configure); > 1463 > > --- > 0-DAY kernel test infrastructure Open Source Technology Center > https://lists.01.org/pipermail/kbuild-all Intel Corporation
WARNING: multiple messages have this Message-ID (diff)
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 3/5] ACPI: Introduce DMA ranges parsing Date: Sun, 6 Aug 2017 10:42:20 +0100 [thread overview] Message-ID: <20170806094219.GA16298@red-moon> (raw) In-Reply-To: <201708061311.4aEB8P1Q%fengguang.wu@intel.com> On Sun, Aug 06, 2017 at 01:12:55PM +0800, kbuild test robot wrote: > Hi Lorenzo, > > [auto build test ERROR on pm/linux-next] > [also build test ERROR on v4.13-rc3 next-20170804] > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] > > url: https://github.com/0day-ci/linux/commits/Lorenzo-Pieralisi/ACPICA-resource_mgr-Allow-_DMA-method-in-walk-resources/20170804-185152 > base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next > config: ia64-allnoconfig (attached as .config) > compiler: ia64-linux-gcc (GCC) 6.2.0 > reproduce: > wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # save the attached .config to linux build tree > make.cross ARCH=ia64 > > Note: the linux-review/Lorenzo-Pieralisi/ACPICA-resource_mgr-Allow-_DMA-method-in-walk-resources/20170804-185152 HEAD 37e91dddbbeb771d4df0001f716607f1dd8719f8 builds fine. > It only hurts bisectibility. Sigh, it is a silly v2->v3 rebase mistake, a change hunk that should be in patch 4 ended up in patch 3, series as a whole is fine but this must be fixed. Rafael, please let me know the best way to handle this, I think me sending a v4 is the simplest so that you can just update the branch. Apologies and thanks. Lorenzo > All errors (new ones prefixed by >>): > > drivers/acpi/scan.c: In function 'acpi_dma_configure': > >> drivers/acpi/scan.c:1451:2: error: implicit declaration of function 'iort_dma_setup' [-Werror=implicit-function-declaration] > iort_dma_setup(dev, &dma_addr, &size); > ^~~~~~~~~~~~~~ > cc1: some warnings being treated as errors > > vim +/iort_dma_setup +1451 drivers/acpi/scan.c > > 1440 > 1441 /** > 1442 * acpi_dma_configure - Set-up DMA configuration for the device. > 1443 * @dev: The pointer to the device > 1444 * @attr: device dma attributes > 1445 */ > 1446 int acpi_dma_configure(struct device *dev, enum dev_dma_attr attr) > 1447 { > 1448 const struct iommu_ops *iommu; > 1449 u64 dma_addr = 0, size = 0; > 1450 > > 1451 iort_dma_setup(dev, &dma_addr, &size); > 1452 > 1453 iommu = iort_iommu_configure(dev); > 1454 if (IS_ERR(iommu) && PTR_ERR(iommu) == -EPROBE_DEFER) > 1455 return -EPROBE_DEFER; > 1456 > 1457 arch_setup_dma_ops(dev, dma_addr, size, > 1458 iommu, attr == DEV_DMA_COHERENT); > 1459 > 1460 return 0; > 1461 } > 1462 EXPORT_SYMBOL_GPL(acpi_dma_configure); > 1463 > > --- > 0-DAY kernel test infrastructure Open Source Technology Center > https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2017-08-06 9:40 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-03 12:32 [PATCH v3 0/5] ACPI: DMA ranges management Lorenzo Pieralisi 2017-08-03 12:32 ` Lorenzo Pieralisi 2017-08-03 12:32 ` [PATCH v3 1/5] ACPICA: resource_mgr: Allow _DMA method in walk resources Lorenzo Pieralisi 2017-08-03 12:32 ` Lorenzo Pieralisi 2017-08-03 12:32 ` [PATCH v3 2/5] ACPI: Make acpi_dev_get_resources() method agnostic Lorenzo Pieralisi 2017-08-03 12:32 ` Lorenzo Pieralisi 2017-08-03 12:32 ` [PATCH v3 3/5] ACPI: Introduce DMA ranges parsing Lorenzo Pieralisi 2017-08-03 12:32 ` Lorenzo Pieralisi 2017-08-06 5:12 ` kbuild test robot 2017-08-06 5:12 ` kbuild test robot 2017-08-06 5:12 ` kbuild test robot 2017-08-06 9:42 ` Lorenzo Pieralisi [this message] 2017-08-06 9:42 ` Lorenzo Pieralisi 2017-08-06 11:21 ` Rafael J. Wysocki 2017-08-06 11:21 ` Rafael J. Wysocki 2017-08-06 11:21 ` Rafael J. Wysocki 2017-08-03 12:32 ` [PATCH v3 4/5] ACPI: Make acpi_dma_configure() DMA regions aware Lorenzo Pieralisi 2017-08-03 12:32 ` Lorenzo Pieralisi 2017-08-03 12:32 ` [PATCH v3 5/5] ACPI/IORT: Add IORT named component memory address limits Lorenzo Pieralisi 2017-08-03 12:32 ` Lorenzo Pieralisi 2017-08-03 13:25 ` [PATCH v3 0/5] ACPI: DMA ranges management Hanjun Guo 2017-08-03 13:25 ` Hanjun Guo 2017-08-03 13:25 ` Hanjun Guo 2017-08-03 15:16 ` Will Deacon 2017-08-03 15:16 ` Will Deacon 2017-08-03 15:45 ` Nate Watterson 2017-08-03 15:45 ` Nate Watterson 2017-08-03 17:21 ` Robin Murphy 2017-08-03 17:21 ` Robin Murphy 2017-08-09 21:14 ` Jeremy Linton 2017-08-09 21:14 ` Jeremy Linton 2017-08-11 8:52 ` Lorenzo Pieralisi 2017-08-11 8:52 ` Lorenzo Pieralisi 2017-08-14 18:41 ` Feng Kan 2017-08-14 18:41 ` Feng Kan 2017-08-14 18:41 ` Feng Kan 2017-11-30 7:28 ` Feng Kan 2017-11-30 7:28 ` Feng Kan 2017-11-30 7:28 ` Feng Kan 2017-12-01 0:43 ` Feng Kan 2017-12-01 0:43 ` Feng Kan 2017-12-01 0:43 ` Feng Kan 2017-12-01 10:39 ` Lorenzo Pieralisi 2017-12-01 10:39 ` Lorenzo Pieralisi 2017-12-01 10:39 ` Lorenzo Pieralisi
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=20170806094219.GA16298@red-moon \ --to=lorenzo.pieralisi@arm.com \ --cc=fkan@apm.com \ --cc=hanjun.guo@linaro.org \ --cc=jcm@redhat.com \ --cc=kbuild-all@01.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@intel.com \ --cc=nwatters@codeaurora.org \ --cc=rjw@rjwysocki.net \ --cc=robert.moore@intel.com \ --cc=robin.murphy@arm.com \ --cc=rui.zhang@intel.com \ --cc=will.deacon@arm.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: linkBe 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.