Linux Media Controller development
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Mauro Carvalho Chehab <m.chehab@samsung.com>,
	linux-media@vger.kernel.org
Subject: Re: [linuxtv-media:master 7661/7664] ERROR: "omapdss_compat_init" [drivers/media/platform/omap/omap-vout.ko] undefined!
Date: Wed, 26 Nov 2014 08:50:41 +0100	[thread overview]
Message-ID: <1416988241.29407.5.camel@x220> (raw)
In-Reply-To: <201411260931.8e2dBfm8%fengguang.wu@intel.com>

Hi Fengguang,

On Wed, 2014-11-26 at 09:34 +0800, kbuild test robot wrote:
> tree:   git://linuxtv.org/media_tree.git master
> head:   504febc3f98c87a8bebd8f2f274f32c0724131e4
> commit: 6b213e81ddf8b265383c9a1a1884432df88f701e [7661/7664] [media] omap: Fix typo "HAS_MMU"
> config: m68k-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
>   git checkout 6b213e81ddf8b265383c9a1a1884432df88f701e
>   # save the attached .config to linux build tree
>   make.cross ARCH=m68k 

This is the first time I've made the kbuild test robot trip. So I'm not
sure how to interpret this.

Is ARCH=m68k the only build that failed through this commit? Or is it
the first build that failed? If so, how can I determine which arches
build correctly?

> All error/warnings:
> 
> >> ERROR: "omapdss_compat_init" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dss_get_overlay_manager" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dss_get_num_overlay_managers" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dss_get_overlay" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omapdss_is_initialized" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dispc_register_isr" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omapdss_get_version" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dss_put_device" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dss_get_next_device" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dispc_unregister_isr" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omapdss_compat_uninit" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dss_get_device" [drivers/media/platform/omap/omap-vout.ko] undefined!
> >> ERROR: "omap_dss_get_num_overlays" [drivers/media/platform/omap/omap-vout.ko] undefined!
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

Thanks,

Paul Bolle


  reply	other threads:[~2014-11-26  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  1:34 [linuxtv-media:master 7661/7664] ERROR: "omapdss_compat_init" [drivers/media/platform/omap/omap-vout.ko] undefined! kbuild test robot
2014-11-26  7:50 ` Paul Bolle [this message]
2014-11-26 12:26   ` Mauro Carvalho Chehab
2014-11-26 19:30   ` Fengguang Wu
2014-11-26 20:22     ` Paul Bolle

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=1416988241.29407.5.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.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