From: Okaya@codeaurora.org
To: kbuild test robot <lkp@intel.com>
Cc: Sinan Kaya <okaya@codeaurora.org>,
kbuild-all@01.org, dmaengine@vger.kernel.org,
mark.rutland@arm.com, timur@codeaurora.org,
devicetree@vger.kernel.org, cov@codeaurora.org,
vinod.koul@intel.com, jcm@redhat.com, agross@codeaurora.org,
arnd@arndb.de, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V10 7/7] dma: qcom_hidma: add support for object hierarchy
Date: Mon, 21 Dec 2015 22:05:24 -0000 [thread overview]
Message-ID: <2c12e9aadc42c51a37e6dd771652aafb.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <201512191503.k4p1BXza%fengguang.wu@intel.com>
> Hi Sinan,
>
> [auto build test ERROR on v4.4-rc5]
> [also build test ERROR on next-20151218]
>
> url:
> https://github.com/0day-ci/linux/commits/Sinan-Kaya/dma-add-Qualcomm-Technologies-HIDMA-driver/20151218-010637
> config: sparc64-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=sparc64
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "of_irq_parse_one" [drivers/dma/qcom/hdma_mgmt.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology
> Center
> https://lists.01.org/pipermail/kbuild-all Intel
> Corporation
>
I am confused about this. The function call is made only if OF is defined.
The function that is being called is defined with extern symbol and
resides in drivers/of/irq.c. how does the sparc arch define OF yet exclude
drivers/of/irq.c
next prev parent reply other threads:[~2015-12-21 22:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 17:01 [PATCH V10 0/7] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2015-12-17 17:01 ` [PATCH V10 1/7] dma: qcom_bam_dma: move to qcom directory Sinan Kaya
2015-12-17 17:01 ` [PATCH V10 2/7] dma: hidma: Add Device Tree support Sinan Kaya
2015-12-19 4:17 ` Rob Herring
2015-12-21 22:01 ` Okaya
2015-12-17 17:01 ` [PATCH V10 3/7] dma: add Qualcomm Technologies HIDMA management driver Sinan Kaya
2015-12-17 17:01 ` [PATCH V10 4/7] dma: add Qualcomm Technologies HIDMA channel driver Sinan Kaya
2015-12-17 17:01 ` [PATCH V10 5/7] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2015-12-17 17:01 ` [PATCH V10 6/7] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2015-12-17 17:01 ` [PATCH V10 7/7] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
2015-12-19 7:14 ` kbuild test robot
2015-12-19 7:37 ` kbuild test robot
2015-12-21 22:05 ` Okaya [this message]
[not found] ` <1450371684-23415-8-git-send-email-okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-12-19 18:37 ` Andy Shevchenko
2015-12-21 22:05 ` Timur Tabi
2015-12-30 15:28 ` Sinan Kaya
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=2c12e9aadc42c51a37e6dd771652aafb.squirrel@www.codeaurora.org \
--to=okaya@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jcm@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=timur@codeaurora.org \
--cc=vinod.koul@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 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).