From: Oded Gabbay <oded.gabbay@gmail.com>
To: Roman Gushchin <guro@fb.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [rgushchin:release_percpu 321/401] ERROR: "dma_fence_release" [drivers/misc/habanalabs/habanalabs.ko] undefined!
Date: Sat, 2 Mar 2019 11:09:09 +0200 [thread overview]
Message-ID: <CAFCwf10c_rjZTDmDnDhH4wjihV8PhO=PSN2mwCwU6cB7+fx-5Q@mail.gmail.com> (raw)
In-Reply-To: <201903020948.mXKq6Z2s%fengguang.wu@intel.com>
On Sat, Mar 2, 2019 at 3:42 AM kbuild test robot <lkp@intel.com> wrote:
>
> Hi Andrew,
>
> First bad commit (maybe != root cause):
>
> tree: https://github.com/rgushchin/linux.git release_percpu
> head: 8b287c57af99a4642cdf70b3b1a5ab1d90877bba
> commit: 773ae09cc9c61b8f7dc983e9a1d4ce5abbd6339d [321/401] linux-next-rejects
> config: x86_64-randconfig-m3-02280836 (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-5) 7.4.0
> reproduce:
> git checkout 773ae09cc9c61b8f7dc983e9a1d4ce5abbd6339d
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "dma_fence_release" [drivers/misc/habanalabs/habanalabs.ko] undefined!
> >> ERROR: "dma_fence_init" [drivers/misc/habanalabs/habanalabs.ko] undefined!
> >> ERROR: "dma_fence_signal" [drivers/misc/habanalabs/habanalabs.ko] undefined!
> >> ERROR: "dma_fence_default_wait" [drivers/misc/habanalabs/habanalabs.ko] undefined!
> >> ERROR: "dma_fence_wait_timeout" [drivers/misc/habanalabs/habanalabs.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
Hi Roman and Andrew.
That error comes from the original patch-set of the driver, where a
there was missing "select DMA_SHARED_BUFFER" in Kconfig. So for
certain configurations, the build would fail.
This is already fixed in the current char-misc-next tree of gkh.
Thanks,
Oded
next prev parent reply other threads:[~2019-03-02 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 1:41 kbuild test robot
2019-03-02 9:09 ` Oded Gabbay [this message]
2019-03-02 22:19 ` Roman Gushchin
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='CAFCwf10c_rjZTDmDnDhH4wjihV8PhO=PSN2mwCwU6cB7+fx-5Q@mail.gmail.com' \
--to=oded.gabbay@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.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