From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, mhocko@suse.cz,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: mmotm 2014-09-25-16-28 uploaded (media/platform/vivid)
Date: Fri, 26 Sep 2014 10:29:58 -0700 [thread overview]
Message-ID: <5425A296.3090900@infradead.org> (raw)
In-Reply-To: <5424a53b.o+nym6SX0Tg7EdW6%akpm@linux-foundation.org>
On 09/25/14 16:28, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2014-09-25-16-28 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
on i386, when CONFIG_FB is not enabled:
ERROR: "cfb_fillrect" [drivers/media/platform/vivid/vivid.ko] undefined!
ERROR: "cfb_imageblit" [drivers/media/platform/vivid/vivid.ko] undefined!
ERROR: "fb_alloc_cmap" [drivers/media/platform/vivid/vivid.ko] undefined!
ERROR: "register_framebuffer" [drivers/media/platform/vivid/vivid.ko] undefined!
ERROR: "fb_dealloc_cmap" [drivers/media/platform/vivid/vivid.ko] undefined!
ERROR: "cfb_copyarea" [drivers/media/platform/vivid/vivid.ko] undefined!
ERROR: "unregister_framebuffer" [drivers/media/platform/vivid/vivid.ko] undefined!
I guess that VIDEO_VIVID should depend on FB.
--
~Randy
prev parent reply other threads:[~2014-09-26 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 23:28 mmotm 2014-09-25-16-28 uploaded akpm
2014-09-26 7:31 ` Guenter Roeck
2014-09-26 16:54 ` mmotm 2014-09-25-16-28 uploaded (nf_nat_masquerade_ipv4.c) Randy Dunlap
2014-09-26 17:03 ` Arturo Borrero Gonzalez
2014-09-26 17:45 ` Pablo Neira Ayuso
2014-09-26 17:29 ` Randy Dunlap [this message]
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=5425A296.3090900@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--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).