From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for January 14 (vmwgfx)
Date: Thu, 14 Jan 2010 10:58:40 -0800 [thread overview]
Message-ID: <20100114105840.98972cbc.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100114172047.406ebda8.sfr@canb.auug.org.au>
On Thu, 14 Jan 2010 17:20:47 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100113:
When CONFIG_FB=m:
drivers/built-in.o: In function `vmw_fb_close':
(.text+0x9614a): undefined reference to `unregister_framebuffer'
drivers/built-in.o: In function `vmw_fb_close':
(.text+0x9616f): undefined reference to `framebuffer_release'
drivers/built-in.o: In function `vmw_fb_init':
(.text+0x965b6): undefined reference to `framebuffer_alloc'
drivers/built-in.o: In function `vmw_fb_init':
(.text+0x9692a): undefined reference to `register_framebuffer'
drivers/built-in.o: In function `vmw_fb_init':
(.text+0x9696a): undefined reference to `framebuffer_release'
so this driver needs to depend on FB (or select FB -- ugh, although
that's what nouveau does).
And these selects don't do anything when FB is not enabled:
select FB_DEFERRED_IO
select FB_CFB_FILLRECT
select FB_CFB_COPYAREA
select FB_CFB_IMAGEBLIT
---
~Randy
next prev parent reply other threads:[~2010-01-14 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 6:20 linux-next: Tree for January 14 Stephen Rothwell
2010-01-14 18:58 ` Randy Dunlap [this message]
2010-01-17 23:13 ` [PATCH -next] staging/winbond: fix wbusb struct warnings/error Randy Dunlap
2010-01-17 23:15 ` [PATCH -next] ati_pcigart: fix printk format warning Randy Dunlap
2010-01-17 23:17 ` linux-next: Tree for January 14 (drm header files) Randy Dunlap
2010-01-18 2:42 ` 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=20100114105840.98972cbc.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--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