From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-media@vger.kernel.org
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 19 (media/mantis)
Date: Fri, 18 Dec 2009 19:18:59 -0800 [thread overview]
Message-ID: <20091218191859.ca78c2f1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091219110457.d6c5de1f.sfr@canb.auug.org.au>
On Sat, 19 Dec 2009 11:04:57 +1100 Stephen Rothwell wrote:
> Hi all,
>
> I said:
> > News: there will be no linux-next releases until at least Dec 24 and,
> > more likely, Dec 29. Have a Merry Christmas and take a break. :-)
>
> Well, I decided I had time for one more so it will be based in -rc1).
>
> This one has not had the build testing *between* merges, but has had all
> the normal build testing at the end. Since the latter testing showed no
> problems, this just means that there may be more unbisectable points in
> the tree (but that is unlikely).
ERROR: "ir_input_register" [drivers/media/dvb/mantis/mantis_core.ko] undefined!
ERROR: "ir_input_unregister" [drivers/media/dvb/mantis/mantis_core.ko] undefined!
ERROR: "ir_input_init" [drivers/media/dvb/mantis/mantis_core.ko] undefined!
ERROR: "input_free_device" [drivers/media/dvb/mantis/mantis_core.ko] undefined!
ERROR: "input_allocate_device" [drivers/media/dvb/mantis/mantis_core.ko] undefined!
CONFIG_INPUT=n
---
~Randy
next prev parent reply other threads:[~2009-12-19 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 0:04 linux-next: Tree for December 19 Stephen Rothwell
2009-12-19 3:10 ` linux-next: Tree for December 19 (staging/dt3155) Randy Dunlap
2009-12-19 4:47 ` Greg KH
2010-02-11 16:44 ` Randy Dunlap
2010-02-11 16:54 ` Greg KH
2009-12-19 3:18 ` Randy Dunlap [this message]
2009-12-19 17:11 ` linux-next: Tree for December 19 (media/mantis) Manu Abraham
2009-12-19 18:30 ` Randy Dunlap
2009-12-19 8:42 ` linux-next: Tree for December 19 Geert Uytterhoeven
2009-12-23 7:52 ` Stephen Rothwell
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=20091218191859.ca78c2f1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).