public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linus <torvalds@linux-foundation•org>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Andrew Morton <akpm@linux-foundation•org>
Subject: Re: linux-next: origin tree build warning
Date: Fri, 19 Jun 2009 10:45:31 +0200	[thread overview]
Message-ID: <20090619104531.98e9058c.kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <20090619111359.b317a533.sfr@canb.auug.org.au>

Greetings,

Hmm, this would be true if you are using the s1d13xxxfb driver without having supported 2D accel (essentially everything not 13506). Atleast
for bltbit_wait_bitset. The bltbit_fifo_status on the other hand is needed later on
for image blitting, which is coming.

The point is basicly this, all s1d13xxxfb cards should get their 2D acceleration
going so until then this is just an annoying but harmless warning.

Hope that answers your comment.

Best wishes
Kristoffer

On Fri, 19 Jun 2009 11:13:59 +1000
Stephen Rothwell <sfr@canb•auug.org.au> wrote:

> Hi Linus,
> 
> Today's linux-next build (x86_64 allmodconfig) produced this warning:
> 
> drivers/video/s1d13xxxfb.c:420: warning: 'bltbit_wait_bitset' defined but not used
> drivers/video/s1d13xxxfb.c:463: warning: 'bltbit_fifo_status' defined but not used
> 
> Introduced by commit 3ed167af96ed098187ea41353fe02d1af20d38a1 ("fbdev:
> s1d13xxxfb: add accelerated bitblt functions").
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb•auug.org.au
> http://www.canb.auug.org.au/~sfr/
> 


-- 
Kristoffer Ericson <kristoffer.ericson@gmail•com>

  reply	other threads:[~2009-06-19  8:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  1:13 linux-next: origin tree build warning Stephen Rothwell
2009-06-19  8:45 ` Kristoffer Ericson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27  0:09 Stephen Rothwell
2010-01-18  4:05 Stephen Rothwell
2010-01-18  4:14 ` Stephen Rothwell
2010-01-18  4:29   ` Wu, Fengguang
2010-01-18  5:40     ` Stephen Rothwell
2010-01-19  0:12       ` Stephen Rothwell
2010-01-19 21:05         ` Greg KH
2010-01-19 21:11           ` Greg KH
2010-01-19 23:47             ` Stephen Rothwell
     [not found] <20100101112914.41bc5f77.sfr@canb.auug.org.au>
2010-01-01  0:34 ` Linus Torvalds
2010-01-01  1:02   ` Stephen Rothwell
2010-01-01  1:16     ` Rafael J. Wysocki
2009-12-17  0:10 Stephen Rothwell
2009-12-16  3:52 Stephen Rothwell
2009-12-13 23:24 Stephen Rothwell
2009-12-14  7:24 ` Joe Perches
2009-11-29 23:01 Stephen Rothwell
2009-10-30  3:30 Stephen Rothwell
2009-10-11 23:56 Stephen Rothwell
2009-08-25  0:11 Stephen Rothwell
2009-08-25  2:37 ` David Miller
2009-06-23  0:36 Stephen Rothwell
2009-06-22  1:01 [ofa-general] " Stephen Rothwell
2009-06-22  3:11 ` FUJITA Tomonori
2009-06-19  0:27 Stephen Rothwell
2009-06-19  0:28 ` Stephen Rothwell
2009-06-11  1:27 Stephen Rothwell
2009-04-29  4:49 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=20090619104531.98e9058c.kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=torvalds@linux-foundation$(echo .)org \
    /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