linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ismael Luceno <ismael.luceno@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fbmem: Export fb_get_options and (un)register_framebuffer symbols
Date: Sun, 30 Jun 2013 17:54:30 +0000	[thread overview]
Message-ID: <20130630175418.07f024d6@pirotess> (raw)
In-Reply-To: <1372624575-7664-1-git-send-email-ismael.luceno@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

On Sun, 30 Jun 2013 19:42:36 +0200
David Herrmann <dh.herrmann@gmail.com> wrote:
> Hi
> 
> On Sun, Jun 30, 2013 at 10:36 PM, Ismael Luceno
> <ismael.luceno@gmail.com> wrote:
> > Signed-off-by: Ismael Luceno <ismael.luceno@gmail.com>
> > ---
> >  drivers/video/fbmem.c | 3 +++
> >  1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/video/fbmem.c b/drivers/video/fbmem.c
> > index 098bfc6..910909c 100644
> > --- a/drivers/video/fbmem.c
> > +++ b/drivers/video/fbmem.c
> > @@ -1743,6 +1743,7 @@ register_framebuffer(struct fb_info *fb_info)
> >
> >         return ret;
> >  }
> > +EXPORT_SYMBOL(register_framebuffer);
> 
> These EXPORT_SYMBOL() calls should all be available at the end of
> fbmem.c.
> 
> Cheers
> David

I noticed that just after sending the patch :/. Sorry for the noise.
I'm getting the following errors while trying to load ttm and nouveau on
a vanilla kernel:

drm_kms_helper: Unknown symbol register_framebuffer (err 0)
drm_kms_helper: Unknown symbol fb_get_options (err 0)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      parent reply	other threads:[~2013-06-30 17:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 17:36 [PATCH] fbmem: Export fb_get_options and (un)register_framebuffer symbols Ismael Luceno
2013-06-30 17:42 ` David Herrmann
2013-06-30 17:54 ` Ismael Luceno [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=20130630175418.07f024d6@pirotess \
    --to=ismael.luceno@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    /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).