Skip to contentSkip to conversation

imsttfb warnings in 2.6.0-test4

PATCH Stephen M. Kenton 1 participant 1 message Sep 6, 2003 Framebuffer layer

lore
Share & tools
lore
#0 lore raw

Any reason that imsttfb_load_cursor_image and imstt_set_cursor can not be under the same #if 0 as imsttfb_cursor which used to call them? It gets rid of a couple of defined but not used warnings in 2.6.0-test4 For that matter, is the #if 0 being kept for a particular reason?

Untested patch below

smk

video/imsttfb.c renamed from video/imsttfb.c.ori +1 -1
@@ -1084,6 +1084,7 @@
 	while(read_reg_le32(par->dc_regs, SSTATUS) & 0x40);
 }
 
+#if 0
 static int
 imsttfb_load_cursor_image(struct imstt_par *par, int width, int height, __u8 fgc)
 {
@@ -1191,7 +1192,6 @@
 	}
 }
 
-#if 0
 static int 
 imsttfb_cursor(struct fb_info *info, struct fb_cursor *cursor)
 {

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf