mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Wenlin Kang <wenlin.kang@windriver.com>
Cc: kbuild-all@01.org, bhelgaas@google.com,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci: restrict 64-bit pci device to assign resource from behind of max_pfn
Date: Thu, 15 Oct 2015 19:32:18 +0800	[thread overview]
Message-ID: <201510151906.N1BUlpcz%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444906004-2083-1-git-send-email-wenlin.kang@windriver.com>

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

Hi Wenlin,

[auto build test ERROR on pci/next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Wenlin-Kang/pci-restrict-64-bit-pci-device-to-assign-resource-from-behind-of-max_pfn/20151015-184913
config: mips-fuloong2e_defconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=mips 

All errors (new ones prefixed by >>):

   drivers/pci/setup-res.c: In function '__pci_assign_resource':
>> drivers/pci/setup-res.c:224:6: error: 'max_pfn' undeclared (first use in this function)
        (max_pfn + 1) << PAGE_SHIFT : PCIBIOS_MIN_MEM;
         ^
   drivers/pci/setup-res.c:224:6: note: each undeclared identifier is reported only once for each function it appears in

vim +/max_pfn +224 drivers/pci/setup-res.c

   218		 * For 64-bit pci device, assign resource start from the next page
   219		 * boundary above the maximum physical page address
   220		 */
   221		resource_size_t min_iomem;
   222	
   223		min_iomem = (res->flags & IORESOURCE_MEM_64) ?
 > 224					(max_pfn + 1) << PAGE_SHIFT : PCIBIOS_MIN_MEM;
   225		min = (res->flags & IORESOURCE_IO) ? PCIBIOS_MIN_IO : min_iomem;
   226	#else
   227		min = (res->flags & IORESOURCE_IO) ? PCIBIOS_MIN_IO : PCIBIOS_MIN_MEM;

---
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: 16396 bytes --]

  reply	other threads:[~2015-10-15 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 10:46 Wenlin Kang
2015-10-15 11:32 ` kbuild test robot [this message]
2015-10-16  6:28   ` Wenlin Kang
2015-10-15 14:05 ` Bjorn Helgaas
2015-10-16  8:01   ` Wenlin Kang

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=201510151906.N1BUlpcz%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bhelgaas@google.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=wenlin.kang@windriver.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®