linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: kbuild-all@01.org, Linus Torvalds <torvalds@linux-foundation.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Joerg Roedel <jroedel@suse.de>,
	Jacek Lawrynowicz <jacek.lawrynowicz@intel.com>
Subject: Re: [GIT PULL] PCI changes for v4.7
Date: Mon, 23 May 2016 04:29:41 +0800	[thread overview]
Message-ID: <201605230428.CuSyteQX%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160519154946.GA20036@localhost>

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

Hi,

[auto build test ERROR on linus/master]

url:    https://github.com/0day-ci/linux/commits/Bjorn-Helgaas/PCI-changes-for-v4-7/20160519-235212
config: x86_64-rhel (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

Note: the linux-review/Bjorn-Helgaas/PCI-changes-for-v4-7/20160519-235212 HEAD 1e5c1867a5d64bd92babd851c5656d0841652f23 builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   drivers/iommu/amd_iommu.c: In function 'get_alias':
>> drivers/iommu/amd_iommu.c:266:3: error: implicit declaration of function 'pci_add_dma_alias' [-Werror=implicit-function-declaration]
      pci_add_dma_alias(pdev, ivrs_alias & 0xff);
      ^
   cc1: some warnings being treated as errors

vim +/pci_add_dma_alias +266 drivers/iommu/amd_iommu.c

   260		/*
   261		 * If we don't have a PCI DMA alias and the IVRS alias is on the same
   262		 * bus, then the IVRS table may know about a quirk that we don't.
   263		 */
   264		if (pci_alias == devid &&
   265		    PCI_BUS_NUM(ivrs_alias) == pdev->bus->number) {
 > 266			pci_add_dma_alias(pdev, ivrs_alias & 0xff);
   267			pr_info("AMD-Vi: Added PCI DMA alias %02x.%d for %s\n",
   268				PCI_SLOT(ivrs_alias), PCI_FUNC(ivrs_alias),
   269				dev_name(dev));

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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 36559 bytes --]

  reply	other threads:[~2016-05-22 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 15:49 [GIT PULL] PCI changes for v4.7 Bjorn Helgaas
2016-05-22 20:29 ` kbuild test robot [this message]
2016-05-22 20:46 ` Dave Airlie

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=201605230428.CuSyteQX%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=helgaas@kernel.org \
    --cc=jacek.lawrynowicz@intel.com \
    --cc=jroedel@suse.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).