From: Inki Dae <inki.dae@samsung.com>
To: kbuild test robot <lkp@intel.com>, Sam Ravnborg <sam@ravnborg.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: ERROR: "vmf_insert_mixed" [drivers/gpu/drm/exynos/exynosdrm.ko] undefined!
Date: Fri, 2 Aug 2019 17:15:06 +0900 [thread overview]
Message-ID: <d1ba546e-11d1-3f16-aba8-10ffd318a3f3@samsung.com> (raw)
In-Reply-To: <201907250623.Lvc2mgUO%lkp@intel.com>
Hi,
19. 7. 25. 오전 7:35에 kbuild test robot 이(가) 쓴 글:
> tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: bed38c3e2dca01b358a62b5e73b46e875742fd75
> commit: 156bdac99061b4013c8e47799c6e574f7f84e9f4 drm/exynos: trigger build of all modules
> date: 4 weeks ago
> config: h8300-allmodconfig (attached as .config)
> compiler: h8300-linux-gcc (GCC) 7.4.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 156bdac99061b4013c8e47799c6e574f7f84e9f4
> # save the attached .config to linux build tree
> GCC_VERSION=7.4.0 make.cross ARCH=h8300
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "vmf_insert_mixed" [drivers/gpu/drm/exynos/exynosdrm.ko] undefined!
With below patch I think the build error reported already will be fixed,
https://patchwork.kernel.org/patch/11035147/
Thanks,
Inki Dae
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
next prev parent reply other threads:[~2019-08-02 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190724223620epcas3p35a32100b839a0d545e910e3ed84047ca@epcas3p3.samsung.com>
2019-07-24 22:35 ` kbuild test robot
2019-08-02 8:15 ` Inki Dae [this message]
2019-08-02 10:49 ` Sam Ravnborg
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=d1ba546e-11d1-3f16-aba8-10ffd318a3f3@samsung.com \
--to=inki.dae@samsung.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®