On Tue, Mar 10, 2015 at 10:34:43PM +0100, Geert Uytterhoeven wrote: > Gcc < 4.3 doesn't understand binary constants (0b*): > > drivers/staging/fbtft/fbtft-sysfs.c:156:19: error: invalid suffix "b111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:159:3: error: invalid suffix "b1111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:159:11: error: invalid suffix "b1111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:159:19: error: invalid suffix "b11111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:159:28: error: invalid suffix "b1111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:159:36: error: invalid suffix "b1111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:159:44: error: invalid suffix "b1111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:159:52: error: invalid suffix "b11111" on > integer constant > drivers/staging/fbtft/fb_hx8340bn.c:160:3: error: invalid suffix "b111" on > integer constant > ... > > Hence use hexadecimal constants (0x*) instead. > > Signed-off-by: Geert Uytterhoeven <ge...@linux-m68k.org> > --- > This is against v4.0-rc3. In next-20150310 there are two whitespace > differences.
Can you make it against -next? I can't get this to apply as-is, sorry. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
