From: lkp@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pci: Add and use PCI_GENERIC_SETUP Kconfig entry
Date: Mon, 26 Jun 2017 13:39:24 +0800 [thread overview]
Message-ID: <201706261344.OUjMGlsQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170623220857.28774-2-palmer@dabbelt.com>
Hi Palmer,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc6]
[cannot apply to next-20170623]
[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/Palmer-Dabbelt/pci-Add-and-use-PCI_GENERIC_SETUP-Kconfig-entry/20170626-043558
config: m68k-allnoconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 4.9.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=m68k
All warnings (new ones prefixed by >>):
warning: (M68K) selects PCI_GENERIC_SETUP which has unmet direct dependencies (MMU)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 4487 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170626/d0028190/attachment.gz>
next prev parent reply other threads:[~2017-06-26 5:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 21:45 [PATCH] pci: Add and use PCI_GENERIC_SETUP Kconfig entry Palmer Dabbelt
2017-06-23 22:01 ` James Hogan
2017-06-23 22:08 ` Palmer Dabbelt
2017-06-23 22:08 ` Palmer Dabbelt
2017-06-24 15:08 ` Richard Henderson
2017-06-26 5:39 ` kbuild test robot [this message]
2017-06-26 7:26 ` Geert Uytterhoeven
2017-06-24 9:14 ` Russell King - ARM Linux
2017-06-24 9:13 ` Russell King - ARM Linux
2017-06-27 23:37 ` Bjorn Helgaas
2017-06-28 0:14 ` Palmer Dabbelt
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=201706261344.OUjMGlsQ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=linux-arm-kernel@lists.infradead.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