public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead•org>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-media@vger•kernel.org, linux-next@vger•kernel.org,
	LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for January 5 (multimedia #2)
Date: Tue, 6 Jan 2009 09:39:10 -0200	[thread overview]
Message-ID: <20090106093910.1bdd3611@pedra.chehab.org> (raw)
In-Reply-To: <20090105120657.f5edf279.randy.dunlap@oracle.com>

On Mon, 5 Jan 2009 12:06:57 -0800
Randy Dunlap <randy.dunlap@oracle•com> wrote:

> On Mon, 5 Jan 2009 17:35:17 +1100 Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
> > 
> > Changes since 20090102:
> 
> With CONFIG_INPUT=n and
> CONFIG_DVB_DM1105=m
> CONFIG_DVB_FIREDTV=m:
> 
> ERROR: "input_event" [drivers/media/dvb/firesat/firedtv.ko] undefined!
> ERROR: "input_register_device" [drivers/media/dvb/firesat/firedtv.ko] undefined!
> ERROR: "input_free_device" [drivers/media/dvb/firesat/firedtv.ko] undefined!
> ERROR: "input_unregister_device" [drivers/media/dvb/firesat/firedtv.ko] undefined!
> ERROR: "input_allocate_device" [drivers/media/dvb/firesat/firedtv.ko] undefined!
> ERROR: "input_event" [drivers/media/dvb/dm1105/dm1105.ko] undefined!
> ERROR: "input_free_device" [drivers/media/dvb/dm1105/dm1105.ko] undefined!
> ERROR: "input_register_device" [drivers/media/dvb/dm1105/dm1105.ko] undefined!
> ERROR: "input_allocate_device" [drivers/media/dvb/dm1105/dm1105.ko] undefined!
> ERROR: "input_unregister_device" [drivers/media/dvb/dm1105/dm1105.ko] undefined!
> 
Also fixed by the same patch for the previous report. It were just a matter to
make DVB_DM1105 dependent of INPUT.

Cheers,
Mauro

  reply	other threads:[~2009-01-06 11:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05  6:35 linux-next: Tree for January 5 Stephen Rothwell
2009-01-05 17:45 ` linux-next: Tree for January 5 (dm-target) Randy Dunlap
2009-01-06  3:45   ` Cheng Renquan
2009-01-05 20:04 ` linux-next: Tree for January 5 (multimedia build errors) Randy Dunlap
2009-01-06 11:35   ` Mauro Carvalho Chehab
2009-01-05 20:06 ` linux-next: Tree for January 5 (multimedia #2) Randy Dunlap
2009-01-06 11:39   ` Mauro Carvalho Chehab [this message]
2009-01-05 20:09 ` linux-next: Tree for January 5 (multimedia #3) Randy Dunlap
2009-01-07  0:36   ` Mauro Carvalho Chehab
2009-01-07 18:34     ` Randy Dunlap
2009-01-07 23:27       ` Mauro Carvalho Chehab
2009-01-07 23:36         ` Randy Dunlap
2009-01-05 20:11 ` [PATCH -next] jbd2: fix printk format warning Randy Dunlap
2009-01-11 18:52   ` Simon Holm Thøgersen
2009-01-11 19:07     ` Randy Dunlap
2009-01-11 19:20       ` Simon Holm Thøgersen
2009-01-05 21:41 ` dm_attr_{name,uuid}_show buffer overflow? (was: Re: linux-next: Tree for January 5) Geert Uytterhoeven
2009-01-05 22:18   ` strncat() misuse (was: Re: dm_attr_{name,uuid}_show buffer overflow? (was: Re: linux-next: Tree for January 5)) Geert Uytterhoeven
2009-01-06  1:27     ` Alasdair G Kergon
2009-01-06  2:16       ` Alasdair G Kergon
2009-01-07 14:39     ` Laurent Pinchart

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=20090106093910.1bdd3611@pedra.chehab.org \
    --to=mchehab@infradead$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-media@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=randy.dunlap@oracle$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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