From: zajec5@gmail.com (Rafał Miłecki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] PCI: iproc: Support DT property for ignoring aborts when probing
Date: Sun, 10 Apr 2016 12:54:22 +0200 [thread overview]
Message-ID: <CACna6rzz+j6GONeh31xOfX+MuHERxAz9z9fREwZXp2=7Xodknw@mail.gmail.com> (raw)
In-Reply-To: <201604101000.oQktaJEg%fengguang.wu@intel.com>
On 10 April 2016 at 04:59, kbuild test robot <lkp@intel.com> wrote:
> [auto build test ERROR on pci/next]
> [also build test ERROR on v4.6-rc2 next-20160408]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/PCI-iproc-Support-DT-property-for-ignoring-aborts-when-probing/20160410-055241
> base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
> config: arm-allmodconfig (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=arm
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "hook_fault_code" [drivers/pci/host/pcie-iproc.ko] undefined!
Oh, it seems hook_fault_code is not an exported SYMBOL and can't be
used when building iproc as module.
Any idea how to resolve this problem?
--
Rafa?
next prev parent reply other threads:[~2016-04-10 10:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 21:50 [PATCH 1/2] PCI: iproc: Support DT property for ignoring aborts when probing Rafał Miłecki
2016-04-09 21:50 ` [PATCH 2/2] PCI: iproc: Enable hooking abort handler on devices with bcma Rafał Miłecki
2016-04-10 2:59 ` [PATCH 1/2] PCI: iproc: Support DT property for ignoring aborts when probing kbuild test robot
2016-04-10 10:54 ` Rafał Miłecki [this message]
2016-04-11 1:43 ` Florian Fainelli
2016-04-11 20:06 ` Ray Jui
2016-04-11 21:55 ` Florian Fainelli
2016-04-11 22:24 ` Ray Jui
2016-04-11 22:26 ` Scott Branden
2016-04-11 22:34 ` Ray Jui
2016-04-11 22:41 ` Florian Fainelli
2016-04-11 22:51 ` Ray Jui
2016-04-11 22:51 ` Florian Fainelli
2016-04-17 15:54 ` Rafał Miłecki
2016-04-17 14:02 ` Arnd Bergmann
2016-04-18 17:47 ` Ray Jui
2016-04-20 18:18 ` Ray Jui
2016-10-28 15:31 ` Rafał Miłecki
2016-10-28 16:58 ` Ray Jui
2016-10-28 17:04 ` Florian Fainelli
2016-10-29 6:14 ` Rafał Miłecki
2016-04-11 8:57 ` Mark Rutland
2016-04-17 15:43 ` Rafał Miłecki
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='CACna6rzz+j6GONeh31xOfX+MuHERxAz9z9fREwZXp2=7Xodknw@mail.gmail.com' \
--to=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).