All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	devel@driverdev.osuosl.org
Subject: Re: [PATCH -next] staging/vmwgfx: depends on FB
Date: Tue, 16 Feb 2010 15:05:37 -0800	[thread overview]
Message-ID: <20100216230537.GA19450@suse.de> (raw)
In-Reply-To: <4B7B233F.9000507@oracle.com>

On Tue, Feb 16, 2010 at 02:59:11PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> vmwfgx uses framebuffer interfaces, so it should depend on FB.
> Otherwise it has these build errors (e.g., when CONFIG_FB=m):
> 
> drivers/built-in.o: In function `vmw_fb_close':
> (.text+0x97713): undefined reference to `unregister_framebuffer'
> drivers/built-in.o: In function `vmw_fb_close':
> (.text+0x97754): undefined reference to `framebuffer_release'
> drivers/built-in.o: In function `vmw_fb_init':
> (.text+0x97e1c): undefined reference to `framebuffer_alloc'
> drivers/built-in.o: In function `vmw_fb_init':
> (.text+0x9838d): undefined reference to `register_framebuffer'
> drivers/built-in.o: In function `vmw_fb_init':
> (.text+0x9842a): undefined reference to `framebuffer_release'
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  drivers/gpu/drm/vmwgfx/Kconfig |    2 +-

This is not a drivers/staging/* file, so there's not much I can do with
it.  It belongs to David Airlie.

thanks,

greg k-h

  reply	other threads:[~2010-02-16 23:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  7:55 linux-next: Tree for February 16 Stephen Rothwell
2010-02-16 22:59 ` [PATCH -next] staging/rtl8187se: needs semaphore.h Randy Dunlap
2010-02-16 22:59 ` [PATCH -next] staging/vmwgfx: depends on FB Randy Dunlap
2010-02-16 23:05   ` Greg KH [this message]
2010-02-16 23:15     ` Randy Dunlap
2010-02-16 23:22       ` Greg KH
2010-02-17  0:05         ` Randy Dunlap

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=20100216230537.GA19450@suse.de \
    --to=gregkh@suse.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.