mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Oza Pawandeep <oza.oza@broadcom.com>
Cc: kbuild-all@01.org, Joerg Roedel <joro@8bytes.org>,
	Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	Oza Pawandeep <oza.pawandeep@gmail.com>,
	Oza Pawandeep <oza.oza@broadcom.com>
Subject: Re: [PATCH v5 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges
Date: Mon, 8 May 2017 03:08:24 +0800	[thread overview]
Message-ID: <201705080258.8tzPFTzu%fengguang.wu@intel.com> (raw)
In-Reply-To: <1493992827-1553-4-git-send-email-oza.oza@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

Hi Oza,

[auto build test ERROR on v4.9-rc8]
[cannot apply to glikely/devicetree/next iommu/next next-20170505]
[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/Oza-Pawandeep/OF-PCI-address-PCI-inbound-memory-limitations/20170508-004625
config: arm-arm67 (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
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=arm 

All errors (new ones prefixed by >>):

   drivers//of/address.c: In function 'of_bus_pci_get_dma_ranges':
>> drivers//of/address.c:212:2: error: implicit declaration of function 'pci_free_resource_list' [-Werror=implicit-function-declaration]
     pci_free_resource_list(&res);
     ^~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/pci_free_resource_list +212 drivers//of/address.c

   206				*dma_addr = res_dma->start - window->offset;
   207				*paddr = res_dma->start;
   208				*size = resource_size(res_dma);
   209				}
   210			}
   211		}
 > 212		pci_free_resource_list(&res);
   213	
   214		/*
   215		 * return the largest possible size,

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30170 bytes --]

      reply	other threads:[~2017-05-07 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 14:00 [PATCH v5 0/3] OF/PCI address PCI inbound memory limitations Oza Pawandeep
2017-05-05 14:00 ` [PATCH v5 1/3] of/pci/dma: fix DMA configuration for PCI masters Oza Pawandeep
2017-05-05 14:00 ` [PATCH v5 2/3] iommu/pci: reserve IOVA " Oza Pawandeep
2017-05-05 14:00 ` [PATCH v5 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges Oza Pawandeep
2017-05-07 19:08   ` kbuild test robot [this message]

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=201705080258.8tzPFTzu%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=kbuild-all@01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=oza.oza@broadcom.com \
    --cc=oza.pawandeep@gmail.com \
    --cc=robin.murphy@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: 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

all inboxes | Powered by JetHome®