linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: James Simmons <jsimmons@infradead.org>
Cc: benh@kernel.crashing.org, geert@linux-m68k.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: New fb.h header
Date: Sat, 31 Jan 2004 16:49:55 -0800	[thread overview]
Message-ID: <20040131164955.456d13e2.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401302353290.22830-100000@phoenix.infradead.org>

James Simmons <jsimmons@infradead.org> wrote:
>
> This header patch fixes the issue of building userland apps with fb.h. It 
>  also makes struct fb_pixmap a internal kernel object. Please apply.

It breaks the ppc64 build.



drivers/video/cfbfillrect.c:141: warning: implicit declaration of function `__raw_writeq'
drivers/video/cfbfillrect.c:141: warning: implicit declaration of function `__raw_readq'
drivers/video/cfbimgblt.c: In function `color_imageblit':
drivers/video/cfbimgblt.c:110: warning: implicit declaration of function `__raw_readl'
drivers/video/cfbimgblt.c:122: warning: implicit declaration of function `__raw_writel'
drivers/video/cfbcopyarea.c: In function `bitcpy':
drivers/video/cfbcopyarea.c:68: warning: implicit declaration of function `__raw_writeq'
drivers/video/cfbcopyarea.c:68: warning: implicit declaration of function `__raw_readq'
drivers/built-in.o(.text+0x162d44): In function `.bitfill32':
: undefined reference to `.__raw_readq'
drivers/built-in.o(.text+0x162d60): In function `.bitfill32':
: undefined reference to `.__raw_writeq'
drivers/built-in.o(.text+0x162dc0): In function `.bitfill32':
: undefined reference to `.__raw_writeq'
drivers/built-in.o(.text+0x162df4): In function `.bitfill32':
: undefined reference to `.__raw_writeq'
drivers/built-in.o(.text+0x162e08): In function `.bitfill32':
: undefined reference to `.__raw_writeq'
drivers/built-in.o(.text+0x162e1c): In function `.bitfill32':
: undefined reference to `.__raw_writeq'
drivers/built-in.o(.text+0x162e30): more undefined references to `.__raw_writeq' follow
drivers/built-in.o(.text+0x162e9c): In function `.bitfill32':


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-02-01  0:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1075188083.6191.181.camel@gaston>
2004-01-27 20:07 ` Patch for review and testing James Simmons
2004-01-27 21:40   ` Benjamin Herrenschmidt
2004-01-27 22:09     ` James Simmons
2004-01-27 22:17       ` Benjamin Herrenschmidt
2004-01-27 22:59         ` James Simmons
2004-01-28  0:18           ` Benjamin Herrenschmidt
2004-01-28  1:01           ` Benjamin Herrenschmidt
2004-01-28  1:05             ` Benjamin Herrenschmidt
2004-01-29 19:53               ` Cursor patch James Simmons
2004-01-29 20:20                 ` Andrew Morton
2004-01-30 23:54                   ` New fb.h header James Simmons
2004-02-01  0:49                     ` Andrew Morton [this message]
2004-02-01  1:03                       ` Benjamin Herrenschmidt

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=20040131164955.456d13e2.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).