All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wenlin Kang <wenlin.kang@windriver.com>
To: kbuild test robot <lkp@intel.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: Fri, 16 Oct 2015 14:28:41 +0800	[thread overview]
Message-ID: <56209919.8010102@windriver.com> (raw)
In-Reply-To: <201510151906.N1BUlpcz%fengguang.wu@intel.com>

On 2015年10月15日 19:32, kbuild test robot wrote:
> 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


Hi

Thanks you point out this, due to I built it on x86 previously , so 
don't see the error.

After added  "#include <linux/bootmem.h>" in drivers/pci/setup-res.c, it 
will be ok.

-- 
Thanks,
Wenlin Kang


  reply	other threads:[~2015-10-16  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 10:46 [PATCH] pci: restrict 64-bit pci device to assign resource from behind of max_pfn Wenlin Kang
2015-10-15 11:32 ` kbuild test robot
2015-10-16  6:28   ` Wenlin Kang [this message]
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=56209919.8010102@windriver.com \
    --to=wenlin.kang@windriver.com \
    --cc=bhelgaas@google.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.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 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.