Re: [linuxtv-media:master 7661/7664] ERROR: "omapdss_compat_init" [drivers/media/platform/omap/omap-vout.ko] undefined!

[Paul Bolle <pebolle@tiscali.nl>]

Hi Fengguang

On Wed, 2014-11-26 at 11:30 -0800, Fengguang Wu wrote:
> On Wed, Nov 26, 2014 at 08:50:41AM +0100, Paul Bolle wrote:
> > 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?
> 
> It's the first build that failed. I checked log and find these
> failures, which covers m68k, mips and i386.

By now your bot sent its fanmail for those other two architectures too.
So the lesson here is, apparently, to wait a few hours. By then the bots
should have done their thing and I can do damage control.

Luckily, for me, Mauro already has done damage control (see
http://git.linuxtv.org/cgit.cgi/mchehab/media-next.git/commit/?id=7996d58f03c14c0caf9935e64bb32ed04dbe79c5 ). So all I'll have to do now is ponder how to make sure your bot leaves me alone in the future.

Thanks, both of you!


Paul Bolle